Suddenly database cannot be read?

connie

Registered User.
Local time
Yesterday, 20:04
Joined
Aug 6, 2009
Messages
92
Hi,

I was on another computer (same network) today and went to access a database I'm working on creating. When I tried to open it from this different computer, I got an error message I've never seen before. I closed out and later went to access it from my regular computer, but now that same error is being displayed here as well.

This is the error:

"The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted. Deleting the VBA project removes all code from modules, forms and reports. You should back up your database before attempting to open the database and delete the VBA project.

To create a backup copy, click Cancel then make a backup copy of your database. To open the database and delete the VBA project without creating a backup copy, click OK."

I made the backup, then went back to this error and clicked OK, and it grants me access to the database again but deletes ALL VBA code. In the backup I tried various ways to get back into the VBA just to save the code in order to compile/fix it, but it will not allow me to view the code at all and every time I try I just keep getting this same error. I really don't want to start all over again writing this code!! Can anyone help?

The only suggestion I've found so far is to buy some $300 product to fix a corrupted file, which I can't do.
 
Actually, in the sidebar of the file folder window I just tried "Restore previous version," and I was able to restore it all!!! Yay! But any ideas on how to prevent this from happening again in the future? I already did compile the VBA and there weren't any errors; I have a feeling it must have to do with trying to open it from that (SLOW) other computer that couldn't handle it...I've never had that error in Access before.
 
main thing is

a) ensure you have a backup of your database
b) split the database, so only the data is on the server
c) have a backup procedure for the backend
d) give each user their own copy of the frontend

this will minimise the chance of corruption, and definitley minimise the effect of any corruption
 

Users who are viewing this thread

Back
Top Bottom