Database is locked out

[dollarbill]

We have a database that everytime we try to open it, it gives the following error:
"The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time."

I know that this is not possible since I copied the database down to my hard drive and I receive the same error. Also, it won't let me try to import that database into a blank database, it just keeps returning the same error.

Any information would be greatly appreciated. Thanks!

 

[jdegeorge]

Have you tried to repair/compile the database?

Jim DeGeorge

 

[dollarbill]

It won't let us open it up to compact and repair. When I hold the shift down to open it the error message comes up. When we open up Access and select compact and repair and then select the database to compact and repair it brings up the same error. Any other ideas???

 

[jdegeorge]

Microsoft has a repair tool called JetComp.exe that you can download for free. You don't have to open the database directly.

Jim DeGeorge

 

[dollarbill]

I downloaded that utility and I got the error: "Error Compacting database." Any other ideas?

 

[jdegeorge]

Have you tried creating a blank MDB and importing objects from the corrupted MDB? If this doesn't work, I don't believe that you've got any other options.

This happened to me a while back and it was at that point that I started to make daily backups of my MDBs.

Sorry.

Jim DeGeorge

 

[psemianonymous]

The last tip is a good one. I had this error message pop up myself (two different times) when a memo field in a single line of a single table corrupted. Check the Corrupt MDBs FAQ for solutions, besides what jdegeorge has already mentioned.



If you can find the corrupted row and delete it, then your database should work fine from then onwards.

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[dollarbill]

I have already tried to import the tables into a blank mdb and I still received the original error message. I did find some code to try to find the corrupted row, but I was unsuccessful. We are looking into pulling it from a backup. Thanks for all of your help.

 

[jdegeorge]

I feel for you having recently lived through that. Good luck with the backups!

Jim DeGeorge