Is it really possible to convert a very complex Access 2007 database to 2003?

Desperate

Registered User.
Local time
Today, 00:08
Joined
Apr 28, 2010
Messages
51
Hello mates. As subject says I have a very detailed and complex access 2007 application with full of codes, queries etc. Normal convert fails for such an application and if I start to do it again in 2003 it will take a lot of time. So is there a way which I can convert my 2007 database to 2003 without any problem?
 
How are you trying to convert it?
Where is it failing?
Have you tried creating a blank 2003 mdb and importing all the objects into it?
Is it a split database?
 
I have tried to convert it through Microsoft Office Button, and save database to Access 2003 Database.
It takes all tables, forms, queries but none of the VBA codes and queries are working.
Yes I tried and failed same as above.
No it is not a split database.
 
Its more than likely your references in your vba code are no longer found. If you open your code and you click on the menu at the top Tools--> References you might see something that says "Missing: Microsoft Outlook objects 12.0" etc..

The way you should work with that is with each one that is missing de-select it and select the highest version you have available like "Microsoft Outlook objects 11.0".

Just a thought,

TheChazm
 
Thanks I have read the article.
Well some of the forms and queries didn't get converted in to 2003. New featured may cause this as it says in the article. I will go in to details and try to find out.

Secondly, It says there is a missing or broken reference for the file 'msador15.dll' version 6.0.

I fixed this by unchecking the missing library Mic. ActiveX Data Obj. RecSet vers. 6.
 
Well most of the queries are not working. I couldn't find the reason. Is it possible because of missing reference?
 
Its very possible. Are they using an ADODB or DAO connection in your modules? If you look at the top of the modules there should be something like Dim rsc as New ADODB.Recordset or db as Database.

If its ADODB try adding the reference "Microsoft ActiveX Data Objects 2.8 Library".

If its DAO try adding the reference "Microsoft DAO 3.6 Object Library"

Hope this helps,

TheChazm
 
If most of your queries were pulling data from fields that were using the new Access 2007 features then it won't work. If you deleted the fields in the 2007 db, you should have adjusted your queries before converting.

And it's nothing to do with references.
 
I checked references. Both were added. This is related with queries.

How can I understand which are the new features? Can you please give one example?
I know in 2007 there is calender option to enter dates easily but this is not in my fields.
How to identify others ?
 
I can't explain it better than how it is explained in the section "Factors that prevent conversion to an earlier file format" in the link. All the possibilities are listed there, since you created the table you know which fields are using the new data types or features listed in there.

For example, if you were using the Attachment data type and had to delete it, you will also need to delete any fields that reference that field in your queries.

When you say it isn't working, do you get pop-up boxes requesting input?
 

Users who are viewing this thread

Back
Top Bottom