Cannot open Access Database...

[ewomack]

Hello. I haven't seen this before with Access; I've searched the forum and haven't found anything yet...

I have an Access database that was being used by about 9 different people. Everything was going along okay, but one day it became read-only for no reason. Once everyone got out of the DB it said it needed repairing. So with only one person in I ran the repair, but the horror-inducing message "The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time." appears and when I click "OK" on the message nothing happens whatsoever.

Luckily backups existed, but some data was lost. Is there anyway to run a repair on the database that won't open? Or is it a lost cause?

Thank you!

 

[ghudson]

Do all of the users have full permissions to the directory that the db is located in? Each user must have open, edit and delete access to the db file. Search some more for there are tons of threads with similar questions and answers to guide you.

 

[Len Boorman]

Do you have arecord locking strategy in place. Do ypu lock records when available for edit

I would worry about the double edit message

L

 

[The_Doc_Man]

If/when you see that "other user...." message, get out of the DB. Call all users of the DB and tell them to get out. Don't ask. TELL.

Now see if you still have a .LDB file. If there is a way to reboot the system hosting your DB, reboot at the earliest possible convenience. Immediately thereafter, check for the .LDB file. If there is a .LDB file within minutes after a reboot, particularly an after-hours one, you have a "hung" .LDB file. Delete it. If you are going to do this, you MUST emphasize to your users that they will not be able to do anything until you fix the problem, so they must stay the hell out of the DB.

OK, what is going on here?

Some possibilities come to mind.

1. The .LDB file is there because someone's session crashed with that file still open and Windows can't delete it because of a little-known phenomenon called I/O Rundown state. A reboot clears this.

2. The .LDB isn't the culprit, but some Windows File-System lock IS to blame. Again, a reboot clears such locks.

3. You are locking against yourself because of a buried implied query in some function, including something that might be running on a hidden form. Particularly if you have some hidden code on a timer.

4. Someone's permissions in the DB folder are inadequate. As another poster has mentioned, to use an Access DB, you need hefty permissions. If using the "basic" permissions on the folder, you need either "Modify" or "Full Control" to get into the DB. For the "advanced" permissions, you need the ability to create and delete files within the folder. You also need "Read" (or "passthrough") permissions on all folders in the path between your DB folder and the root folder of your shared drive.

Good luck at finding this one. Such problems can be elusive.