2003 MDE does not work in 2002 (XP)

[echorley]

I have created a database using Access 2003. If I leave the database in the MDB format, it will run perfectly on my computer at work that has Access 2002. However, if I use Access 2003 and convert the database to an MDE file, and try to run it at work using Access 2002, I get an error that states "The Visual Basic for Applications project in the database is corrupt."

I know it is not corrupt because the same MDE file runs fine on my machine with Access 2003.

I would like to share the database with some fellow staff members, but I would like it in MDE form.

Any suggestions?

 

[echorley]

Service Pack 3 - no help.

OK, I installed office XP service pack 3 which detailed that it fixed the "corrupt" message.

However, a new error appears when I try to run the MDE: "This database is in an unrecognized format."

Any ideas?

Thanks.

 

[WindSailor]

I believe they have to have Access 2003 to run the MDE file...

Here is Microsofts support article...
Here

http://support.microsoft.com/Default.aspx?kbid=897764

 

[echorley]

Thanks.

That article is frustrating because it gives no reasons, just that Access 2002 SP3 cannot open a Access 2003 MDE database. Weird.

Thanks.

 

[jrjr]

Access has never been backwards compatible, only forwards. This means 02 will not open 03 DB's but 03 will open 02's. When designing your DB, find the oldest version of Access that your users have and build with that version. Either that or upgrade all of your users....

Create your .mde with Access 02. As long as this is the oldest version that your users have, you should be set.

 

[echorley]

Not quite true

I can and do all the time (from home to work) open Access 2003 MDB files in 2002. In Access 2003, when you go to convert the database to a different format, there is no 2002 option, only 2002-2003. This implies that they are backward compatible. The trouble begins when one converts a database in 2003 to an MDE and tries to open it in 2002 as described in the article above.

My work around was to open the database I created in Access 2003 in Access 2002 and create the MDE file in that version, much as you suggested going with the older version. Now the MDE works in both.

 

[jrjr]

Perhaps I should have not said that as I skipped over Access XP (2002). My experience has been in 97, 2000, and 2003. I do know though that you can experience reference issues when opening an 03 database with 2000. The application designed in 03 can have references to libraries that were not in existance in 2000. Maybe you are fortunate and just did not use missing libraries - 02 and 03 may share some, if not all. In any event, If I was in error I apologize!

 

[WindSailor]

Great, glad jrjr got you going.
jrjr has good advice.
To my knowledge MDB files are not compiled code, you can test them to see if they will compile, only MDE files are compiled.
Only guessing here but Access seems to have an auto-correct feature built into it to make it somewhat backward compatible or be able to run and handle errors, or at least run and trap errors. I believe once the code is compiled it makes firm associations to the libraries origianlly used and is not able to handle unforseen errors. Maybe jrjr can expand on this more if needed.

 

[RuralGuy]

WindSailor, I think you will find that MDB files have *both* compiled and source code. MDE files strip out the source and just leave the compiled code. I believe Access only executes compiled code and if you have not compiled it yet, the code is compiled before it is executed. Just thought you'd like to know.

 

[WindSailor]

Thanks for the correction