‘Corrupt’ mde (Access 2003 SP2)

Topic

New Reply

I created an MDB application using Access 2003 SP2 and then created an “MDE” from it to distribute to our users. They all use MS Access 2002. When ever they try to open the executable (mde) version they get the following message: “The Visual Basic for Applications project in the database is corrupt.” I opened the MDB version on the users PC and it works fine. Just the mde is not working. Can this be resolved by changing some of the references in the project, or is there some other element that needs attention.

Many thanks,
aap2

Reply | Quote

Replies

Open the .mdb on one of the users’ PCs.
Activate the Visual Basic Editor.
Select Tools | References…
Do you see one or more references starting with MISSING?
Can you compile the VBA code (Debug | Compile )? Perhaps you used code that is new in Access 2003.
Can you create a working .mde database on such a PC?

Reply | Quote

Hans,
I did as you suggested on the user PC and compiled the MDB without any problem.
I was able to make what appears to be a working executable (still testing on other user desktops).
I didn’t see any MISSING references but I did notice that on my PC I have references to:
Microsoft Access 11 object library and Microsoft Office 11 object library
whereas our users show:
Microsoft Access 10 object library and Microsoft Office 10 object library

Once again, you have been very helpful!
Thanks,
aap2

Reply | Quote

Office XP (aka 2002) = version 10.0
Office 2003 = version 11.0

In general, it’s best to create the .mde in the oldest version you have to support (if you also have Access 2000 users, you should create the .mde on a PC with Access 2000).

Reply | Quote