Record Locking ?

[on-2]

Has anyone had any trouble with intermittent record locking when tring to open a multi user fe / be mdb. I sometimes get the message

"The Microsoft Jet database engine cannot open the file "\\Office3\db\database_be.mdb'. It is already opened exclusively by another user, or you need permission to view its data."

There are two laptops which plug into the network every morning and evening and it seems to be kicked off when these plug in together.

Doesnt seem to be any logical way to unlock anything then it just works a bit later on?.

 

[Lightwave]

File already in use

Came into the office this morning and had exactly the same problem. I've got a live backup of the file so am using that at the moment until we can find time to restart the server. Will let you know what happens...

 

[Pat Hartman]

Make sure that everyone has the necessary network permissions for the db's folder. In particular, the user needs create and delete permissions (which are not normally granted) in order to create and delete the .ldb file. If a user opens the db and doesn't have permission to create the .ldb file and it has not already been created by someone else, Access opens the db in exclusive mode to prevent anyone else from opening the db.

ALL Access databases are secured whether you specifically implement workgroup security or not. Jet handles this by creating an .ldb file when the first user opens a shared db and logging him in silently as "Admin". Changes and record locks are managed in the .ldb. If Access cannot create an .ldb, it cannot manage sharing so it prevents the file from being shared.

 

[on-2]

made some changes

the mad thing is that the db was working ok in its current form for a couple weeks then started to play up.

I have moved the be to another computer on the network and this seems to have cured the problem (must have been something adrift in that folder although read/write permissions were ticked ok, not sure must be XP gone a bit bonkers?) only trouble is it seems to take a lot longer to load the fe now from cold. It is one folder deeper in the tree so I think it is probably this causing it.

Will move up a folder and let you know how I get on for benefit of anyone searching archives in furture. Cheers for suggestions.Alex

 

[NimbusSoftware]

Ah-HA!

Someone had terminated their fe incorrectly. May be they just turned off their computer. In any case there was still a table or query "open". Moving the be to a new directory or disk will clear this.