Orphaned Access Lock File

[blackduck603]

I am having a recurring issue with an Access Lock file that does not get deleted when all users exit the application. It does not look like users are prevented from opening the db, but I want to repair the db and am not sure if this is OK to do with the lock file hanging around.

I was wondering if anyone has any idea why this might be occurring and most importantly is it is OK for me to just delete the lock file in order to open the db.

thanks.......

 

[Rabbie]

Make sure that all users have Delete permissions for the folder where the lock file is stored. If yhey don't then they can't delete the lock file when they exit from the database.

This problem can also occur if some users are not exiting the DB correctly.

If you are sure there is no-one using the lock file you can just delete it. It will be opened when someone opens the DB,

 

[gemma-the-husky]

rabbie is right i think

the ldb file stores names of logged in users. if users dont leave via normal means (eg they crash the app) then they are still "active" as far as the ldb file goes, so the ldb file wont self delete.

if you get a windows error deleting the ldb file then someone IS still using it.

-----------
however - your question indicates all the users are probably sharing/running the SAME copy of the database (on a server?) which is not safe - search on this site for reasons to SPLIT a database

 

[EraserveAP]

I have deleted orphaned ldb files before to no detrimental effect. You should be able to delete it as stated above.