I have an Access DB that I created in Access XP. It works perfectly when used in Access XP. When used in an Access 2003 environment some of the functions don't work anymore. I have users who use Office XP and users who use Office 2003. Does anybody know how to make this DB work in Access 2003 without having to do wholesale code changes?
I have already changed the security to "Low" to bypass the security feature built in in Jet 4.0 but it didn't help. I might have to uninstall Windows XP SP2 to make it work because I know that the application works in an Office 2003 environment with Windows XP SP1 only. But I'm trying to avoid having to uninstall XP SP2 because it's a pain. Any ideas would be greatly appreciated.
Thank you.
My workstation environment is as follows:
OS: Windows XP SP2 Office: Office 2003 SP1 Jet: 4.0
I have an Access db that is going to be shared by two different users. One user has Access 2003 and the other has Access 2002. Will there be any problems using this setup if both the users are accessing the MDB file at the same time?
I'm looking to purchase Access 2002 because that is the version we use at work. The problem is, when I search the net for deals, it is more economical to purchase Office XP 2003 OEM instead of Access 2002.
Is Office XP - version 2002 unless it says Office XP 2003?
Or should I just purchase Office XP 2003 and just convert before I take my database to work? I hear the difference between 2002 and 2003 is mostly the VB coding functionality.
BTW I am looking at the following deal..Hope its not a scam http://www.pricegrabber.com/search_getprod.php/masterid=991291
I have an application which I did in Access 2003 and it uses "Microsoft Access 11.0 Object Library" and also "Microsoft Outlook 11.0 Object Library".
I have converted it to 2002 format from database utilities where it says (2002-2003).
Now when this application is opened in Access 2002 the refrences are "Microsoft Access 10.0 Object Library" and "Microsoft Outlook 10.0 Object Library", now the code starts throwing various errors.
Now what is the way out to avoid these errors? Should I copy the 11.0 libraries and add those in refrences on the machines where access 2002 is available.
I did some initial searching but I am not sure what to search for. I have inherited an access application for maintenance. I am a C# developer by trade so developing code and ui inside the db is kind of weird to me not slamming it, just a little confused with the paradigm. Anyway, I had successfully added functionality to the code base as the per requirements. I made the changes using 2003. No database conversion dialog ever showed so I figured everything was cool. However the client is using 2002 and when they launch it the MDI parent shows the correct title but the form that is opened by default never shows up.
My Access program crashes frequently. I tried the 'Repair Office' function, but that has made no difference. On checking, I see that it's Access 2002, not 2003. Can I still get Access 2003? Should I upgrade to that? I don't want to buy the new Office 2007 suite.
I have discovered a problem with access2003 which is annoying the hell out of me. If any of you out there open up the sample db 'Time and Billing' then go to the preview invoice form, via the clients button on the switchboard, the bottom 4 windows, Total hours, total hourly billing and total expenses give a #Name? error, while the amount due gives an #error? fail. This all works perfectly well in 2002 and I have used it as a basis for a database. Move it over to 2003 and I get the exact same errors.
Does anyone else see these faults and how on earth can I repair them?
I know a bit about using access but I'm not that experienced.
Is it possible that ADO isn't supported in 2002? I use ADO recordsets in a LOT of places...
Is there something idiot-friendly that someone using 2002 can do to register the Version 11.0 object library (ie without re-installing MS Access or requiring the MS Access CDs?)?
Will this issue pop up everywhere that i do non-trivial coding (ie i also use XMLHttp, InternetExplorer.Application ActiveX, etc...
I have written an application which uses a query for the current record and then opens a Word document, merges this record and shows the merged document for the user.
all works fine using Office 2003 - when i try it on a pc with Office 2002 - it diesn't work. Something is happening - WINWORD.EXE is running on the process list. But the document doesn't open. I have added the Microsoft Office 10 Office Library to the references but still no joy.
It's a killer - all testing was done on Office 2003 and now a key user wants to use the app - on 2002 and it doesn't work
Currently my wife has an access 2002 project for work and she would like to work on it at home. We have access 2003, is it possible for her to take the project work on it in access 2003 and then be able to run it again under access 2002? Or should we just look for a copy of access 2002? She can't upgrade the version at work so that's not an option.
Since the last Windows XP update on the secretary PC, all combo lists are now empty even if the related tables are not at all.
Here is her configuration: Windows XP SP 2 Access 2003 SP 3
Here is the description:
1) I've got a combo list based on the table Towns with zip-code, name, country.
2) In the form, in addition the combolist is sorted on the name, just to easily pick up the right Town
3) Since the Windows update, the combo list displays only the zip-code, the other fields are empty even if the table content is not empty at all; I mean I checked in the table content itself.
4) I created a query based on the same arguments of the combo list and the query is working well alone; if I try to create a new combo list linked to the query, then I get the same weird result
5) I've tried to create a new field with the combo list assistant; when I select the table Towns, it shows me the full content (so name, zip, country) and when I run the form, the combo list is again almost empty !!
6) What is more weird is that when I put the Access database back on my standalone laptop which is running Access 2002, the combo list is working correctly !! In fact I am currently maintaining the Access database from my Access 2002 since more than one year and I had no issue
7) In fact, I got the same issue with all the combo-list in my Database
8) I tried to compact the DB but with no effect
Somebody has a brillant idea for me ?? otherwise I think I will contact Mister Bill directly :)
Hi, I have a few Access 2003 databases and I need to open them on my computer which has Access 2000 on it. Can anyone please tell me how to convert it so it is compatible? I have looked into "databse utilities" "convert to" etc but can't figure it out.
I've been hired to clean up and convert a flat filemaker database into access 2003 and I've spent the last two weeks learning the ins and outs of access and doing preparations. Well, today some high up database guy in another department told me not to use access because in the future when a new version of access comes out we will have to recreate the database from scratch because there are lots of problems converting between versions. I'm aware there might be some hiccups but I don't really agree with him. Plus once the database is up and functioning I don't see why we'd even have to upgrade it to a new version. It's just a small health centre patient database with info about patients and their treatments. Does anyone have any opinions about this. Thanks.
I am trying to trouble-shoot an issue with a Access 2002 database. Basically I have the database file shared out on a local network and there are 4 users accessing it. Well, there are using Access 2003 when opening the db file, but every time they exit the db, it is getting corrupted beyond repair.
Any suggestions?
Could it be a version issue? Since I developed it in Access 2002 and they are accessing with a Client 2003ver?
Our Access database is multiple user. The front end is on the local drive and the data file is on our main server. Our database has numerous queries, forms and reports accessed by command buttons or directly. Various queries are set to merge with Word documents.
What are major or annoying problems that have been encountered by converting. Our database is contains our membership information and is crucial to our operation. Detailing problems/solutions if possible would be extremely helpful. Asking for allot but very concerned about conversion. Thanks for any input.
A group in my company has, for quite a while now, used a spreadsheet template to capture information needed for customer hard output. Someone built a page, with the less-than-a-dozen required cells in the appropriate places and a set print area, for printing the information. After they enter the information and print the page, they save the excel file. They have been doing this for quite a while now, and the number of files they have on their shared drive is staggering... and the method they using for naming conventions and cataloging them is almost beyond comprehension.
As they do indeed refer back to these files quite a bit, I am wondering if it possible to import the required cells of information from this mass of excel files, all of which are formatted and laid out the same, to an access table. I have never considered this before and have no idea how to start or whether it is even possible. I did a search on "import" but no results match what I am considering here.
To clarify one thing about these files: The information is not contiguous. It is spread all over... C6, E12, F45, J5, etc. They tried to build the form in excel so that it would print in the format they needed.
I would like to convert a database, which was made for me, in order to enable it to be used on my current system.
I get the error message below when trying to open the database in Microsoft Access 2003.
The database was made using Microsoft Access 2.0.
Will I need Microsoft Access 2.0 to update/delete the database all the time?
Or can I convert this to be used with Microsoft Access 2003?
I have tried opening the file exclusively and I get the same error.
I have selected Show Help and it advises me to import all the objects from the database into a new database. This can`t be achieved as I can`t open the file to retrieve the contents.
http://images6.theimagehosting.com/error.6de.PNG
Thank you very much for your help and all responses are appreciated, Sam
I would like to convert a database, which was made for me, in order to enable it to be used on my current system.
I get the error message below when trying to open the database in Microsoft Access 2003.
The database was made using Microsoft Access 2.0.
Will I need Microsoft Access 2.0 to update/delete the database all the time?
Or can I convert this to be used with Microsoft Access 2003?
I have tried opening the file exclusively and I get the same error.
I have selected Show Help and it advises me to import all the objects from the database into a new database. This can`t be achieved as I can`t open the file to retrieve the contents.
http://images6.theimagehosting.com/error.6de.PNG
Thank you very much for your help and all responses are appreciated, Sam
All.. I have an access 2003 application I have front end and back end separately. When I click "Make MDE File" from tools menu, nothing happens. When checked the Windows Task manager(Windows 2000), CPU usage is 100% and MS ACCESS is not responding. There are no messages.
I created a Workgroup file (Project.mdw), assigned different Permissions to different Groups, and put different Users in appropriate Groups. The above setup is working fine and just as required. But, if I remove or rename the Workgroup file, MS Access does not look for it, creates in its own Workgroup file and starts just as usual - without asking for the Password, or caring about the Permissions and/or restrictions set. How can I make the database file bound to the MDW file, so that it does not open without it.
I have a dbf file that I need to somehow get the table data out of, and into access, excel, or some other usable format. I searches the MS Knowledge Base and read several articles on updating the Jet 4.0 drivers (up to date) and updating Foxpro ODBC drivers, etc. I also searched these forums, and I have yet to find any solution that works.
I think this dbf file might be Foxpro, but I'm not sure. I don't know anything about Foxpro. I was getting an error message "unexpected error from external database driver (8961)", until I read an MS article stating that I should change the name of the Borland folder to BorlandOld and try re-importing. Now Access 2003 just says: "external table not in the specified format".
I created a Workgroup file (Project.mdw), assigned different Permissions to different Groups, and put different Users in appropriate Groups. The above setup is working fine and just as required. But, if I remove or rename the Workgroup file, MS Access does not look for it, creates in its own Workgroup file and starts just as usual - without asking for the Password, or caring about the Permissions and/or restrictions set. How can I make the database file bound to the MDW file, so that it does not open without it.
hello good afternoon. i am trying to open different file types using ms access. the following piece of code i found would only open 'word' documents. how do i make this piece of code more flexible to open pdf documents and excel as well. as it is currently i have a txt field on my form and if the path in the txt fiels leads to a word document when i click a button the word file opens. i want it to open a pdf or excel doc if it was in the txt field
[code] Sub OpenWordDoc(strDocName As String) Dim objApp As Object
'Opens the document
Set objApp = CreateObject("Word.Application") objApp.Visible = True objApp.Documents.Open strDocName