ldb is access.lockfile.9 - ?

[TCerven]

I am using a front end and backend access database with multiple users. The back end is located on the network server and the front ends are created on each user terminal. The system locked up about 2 weeks ago while 2 users were trying to update the same file. I fixed that issue but ever since there is a Access.lockfile.9 on the ldb backend file. Everything is still working ok, however, I fear that it will become a problem sooner or later. I have tried to create a new database and still get the lockfile message. What can I do? :-{}

 

[MoLaker]

Chances are, the ldb file is being held by the network file locking system. You will probably have to delete the ldb file as a network administrator by first removing the network file lock. See your network gurus.

 

[TCerven]

Thanks alot! I will give it a try. :-{}

 

[TCerven]

No good. Additionally, all my users Access 2000 programs have the "Access.lockfile.9" ldb message upon opening a new database from their c:/ drives, including myself.

How could this be? I tried to open a new database with no tables, upon opening after naming it, it get the same ldb extention... "Access.lockfile.9"

Dazed and confussed once again. My network gurus don't have a clue.

 

[MoLaker]

Are all users using the same workgroup (.MDW) file? If so, try switching to a different workgroup file and go through your exercise of creating a new DB. Something has to connect all users and the workgroup file is the only possibility I can think of right now.

If the problem does not occur with a different workgroup file, replace the mdw with a backup. If you don't have a backup (shame, shame) back it up then perform a Repair/compact on it.

 

[TCerven]

All workers are using the same work group .MDW. The front ends are .MDE and I have tried to create new workgroup, database and compact/repair with no avail. I do have a backup copy but hesitate to go there since the database is currently working and hundreds of records would be lost if I dump it. Could there be something locked up on the network itself - or worse - a virus?

 

[MoLaker]

I do not think your data is in jeopardy as long as you maintain backups. I do not believe the problem is in your back-end.

I looked back over this thread and now I'm now sure where we are. Do you have a LDB file with the same name as your back-end database in the directory where your database resides when no one is in the database? Or, do you have a LDB file with the same name as your workgroup file in the same directory where it resides, when no one even has Access open. If the answer is yes to either of these, the LDB file must be deleted - even if it takes the network guys to do it.

"Access.lockfile.9" is the file "type" you will see when you look at a directory containing a LDB file using Explorer. This is normal. When all users close the database, this file should be deleted automatically. If it is not deleted automatically then one of 2 conditions exists. 1) Last user to log out does not have "delete" permissions for the directory. 2) Network file locking systen has the file locked and it cannot be deleted.

This applies to any Access database including MDE's, MDB's, MDA's and MDW's. So, you should also check the LDB file associated with your workgroup file as well. Since you state you get this problem even when trying to create a new database, I'm inclinded to believe it is the workgroup locking file that is causing the problem.

If one of the workstations of the users that had the conflict initially has continuously maintained a network connection since that time, reboot it to make sure it has dropped the database connection.

Lastly, if all else fails, see if you can have the network server rebooted.

Once this problem gets resolved, you need to address the original problem of record conflict. Make sure you have some mode of record locking set on.