Link to home
Create AccountLog in
Avatar of Brian
BrianFlag for United States of America

asked on

Access Database problems

Hello Experts,

I have been asked to move an Access 2000 database to be put on a new desktop computer that runs Office 2013. I believe I got all the files/folders that the Access database consists.

When I try to run the application from Access 2013 I get the following error message below.

Just an FYI, I did not create this database. I was asked be my client to move it to a newer updated system and this new system runs Office 2013.

Message that I receive when trying to run the application:

User generated image
User generated image
User generated image
Avatar of scraby
scraby

sounds like the event handler is not able to interpret these events.  are you able to get into the vb code after these errors?  open the database while pressing left shift.

not sure on compatability between 2000 and 2013 but you may try uninstalling 2013, installing 2000, open the db to make sure all is well and then install 2013 on top of 2000 and see what it does
Avatar of Jim Dettman (EE MVE)
You have broken references.  You need to open the VBA editor window and goto tool/references and see which are missing or broken.

 Once corrected, compile the app and make sure there are no errors.

 The app will run after that.

Jim.
Avatar of Brian

ASKER

@JDettman,

Ok, I'm new to Access. Can you tell me what references are? How would I know what references are missing/broken. Also, what do I need to do to correct the missing/broken references?

Also, how do I compile.
ASKER CERTIFIED SOLUTION
Avatar of scraby
scraby

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
There have been cases as well where references are not listed as "MISSING" or "BROKEN".

If you don't see any like that, check any unchecked reference (doesn't matter which), close the DB and Acces, re-open and uncheck the reference you just checked (it will be the last).  Then do a compile.

That forces a refresh of the references collection in VBA.  If there are any problems, they will come to the surface.

Jim.