Locking File won't disappear!

[musicloverlch]

I have a large Access database and when it closes the locking file won't disappear. I've tried making a fresh database. I've tried Office 2019. I've tried Microsoft 365. Eventually, the database corrupts and I lose all my design work. I have rolled versions newer and older of Office and nothing seems to help. Anyone have anything else I can try?

Thanks,
Laura

[Ulrich Möller]

Hi Laura,

Am 01.05.2023 um 15:27 schrieb musicloverlch:
> I have a large Access database and when it closes the locking file won't disappear. I've tried making a fresh database. I've tried Office 2019. I've tried Microsoft 365. Eventually, the database corrupts and I lose all my design work. I have rolled versions newer and older of Office and nothing seems to help. Anyone have anything else I can try?
>

We can only speculate. It is possible that another error occurs during
closing that can no longer be corrected.

Greetings Ulrich

[Cindy Krist]

Hi Laura,

This happens sometimes.
You can copy the database, then delete the original database, then try to delete the .ldb file.

Here's what I found on the web years ago and it works most of the time:
1. Open the database
2. Create a query and type: "Select A From B;"
3. Run the query; it will throw an error
4. Don't save it
5. Close the db. Then you should be able to delete the .ldb file if it doesn't go away on its own.

Good luck.
Cindy

[James]

Hi Laura -

Is the Access db on a network or local? Just to make sure someone else doesn't have it open, even after you close it.
If, when you close Access, the ldb file persists, will it delete if you manually delete it via Explorer? If not, and you get an error about the file being in use, have you verified that Access is actually closed? (No processes of msaccess.exe still running; check Task Manager).

[James Fortune]

That's a nagging problem that's been with Access Developers for many years. One way to help is to keep a table of users who are logged in. Even doing that, sometimes the lock file persists even after verifying that all users are logged out. For Access databases connected to SQL Server, say on Citrix, I've discovered that rebooting the server allows me to delete the lock file. Server Admins might know other ways to delete the lock file without rebooting. I also use a variable in SQL Server to serve as a shutdown flag. When set, a hidden form on a timer detects the flag and becomes visible to let the user know they have 10 minutes to finish their work before Access shuts them down. The shutdown flag doesn't guarantee that the lock file will become available for deletion when the forced shutdown occurs, but it provides peace of mind that no one will get nuked in the middle of work if a reboot occurs and usually takes care of the situation where a user forgets to log out.