MDE says database needs repair

[Joe Williams]

I have an Access 2002 application. When I convert it to an MDE and send it
to the user, they complain that they get an error messsage that the database
needs to be repaired, do you want to repair it. When they click yes, then it
says there is a problem with the Microsoft jet database and I can't go any
further from there.

If I just send the user the mdb file, they do not have this problem. It is
not machine specific becuase I have had multiple users report this problem,
on different databases.

Can anyone help on why they cannot run the MDE file?

Thanks

Joe

 

[Allen Browne]

Joe this is strange.

You can get this kind of error about the database being corrupt if you use
Access 2003 to create the MDE, and then try to run it on an Access 2002
machine.

If that is not what's happening, could it be an issue with References? What
references do you use? (Tools | References from code window). Could any of
those references be missing from your user's machine, or not correctly
registered there?

It might also be worth checking that they are SP8 for JET 4, though I'm not
sure how it could generate this error message.

Perhaps others have further suggestions.

 

[Joe Williams]

Allen,

I am going from Access 2002 to Access 2002 so I don't think it is the first
issue you described.

As far as references, the references I have on this database are Visual
Basic For Applications, Microsoft Access 10.0 Object Library, Microsoft DAO
3.6 Object Library, OLE Automation, and Microsoft Visual Basic for
Applications Extensibility 5.3.

Are these "standard" references? Are you saying that if I add references
that I have to make sure the client's machine has these as well? how would
he do that with an MDE file where you can't access the code window?

Thanks

- joe

 

[Allen Browne]

Yes: if you add references that the client does not have, the application
will break.

Your first 2 references are required, and you generally need DAO.

OLE Automation is on by default, though most Access apps don't need it.
Do you need the VBA Extensibility lib?
Try droping both of those. If you can still compile the app, you don't need
them.

More info on the files required for the 3 key libraries, their usual
location in each version of Access, and how to re-register:
http://members.iinet.net.au/~allenbrowne/ser-38.html

Trying to code around broken references on startup is quite tricky.
michka's suggestions:
How to guarantee that references will work in your applications
at:
http://www.trigeminal.com/usenet/usenet026.asp?1033