Error Compacting Database

[Moxioron]

Hello all. I think we are in deep doodoo.

I had an analyst call me today because they were getting 'The Microsoft Jet database engine stopped the process because you and another user are attempting to chanbge the same data at the same time'

She was the only one in the database, so I am sure why the message popped up.

What I've done so far to remedy the situation:

1.) Tools/Database Utilities/Compact and Repair
2.) Copy/Paste and msaccess /decompile
3.) Used JETCOMP

When performing 1 and 2 I got the same message as the analyst. When I attempted number 3 I got an 'Error Compacting Database' message.

Any insight as to how I can restore the database or at least have access to the data to create a new database?

Thanks for your help.

 

[Joe4]

Create a new blank database, then import all the objects from your old database into your new one.

 

[Moxioron]

Yep. Already tried that. I get that same Jet database engine message when I select the corrupt database.

 

[Joe4]

Yep. Already tried that. I get that same Jet database engine message when I select the corrupt database.

Hmmm...
That has always worked for me. I wonder if the corruption level is to the extent that it cannot be salvaged. Do you make regular backups of the database that you could restore a backup?

Maybe one of the Access guru's will have some other tricks up their sleeve. You may also want to try Googling "recovering corrupt Access database" and see what comes up.

 

[boblarson]

You might want to go here:
http://www.granite.ab.ca/access/corruptmdbs.htm

 

[SydneyGeek]

Just a thought...
If the db had a crash, maybe the .ldb or .laccdb file stayed behind, and is preventing you from using the db again. With everyone out of the database go looking for the .ldb and delete it if you find it. Then try again.

And 2 cents added to Joe and Bob's suggestions...
Try creating a new, blank database.
Open the old, select each table in turn and try to export it to the new. It's the reverse of Joe's suggestion but sometimes it works when other options don't. If you can get the tables across at least the data is safe.

Then try the forms and reports. Any that won't export are corrupt, and that is usually in the code. I have successfully recovered dud forms / reports by doing this:
1. Go to the form's code module, select all, copy and paste to Notepad.
2. Set the form's HasModule property to No and save the form.
3. Set it back to Yes, then copy and paste the code back from Notepad.

If none of this helps, you'll need a recent backup.
And... is the database split? If not, once it's rebuilt, split it to separate data from application logic. Given that *most* of the corruption I've seen is on the application side, your data is safer.

Denis