“File Already in Use” and Locking Errors in Access
These errors show up when several people use the same database and Access can’t share the file properly. You might see:
- “Could not use ‘[file path]’; file already in use.”
- “The database has been placed in a state by user ‘Admin’ on machine ‘[name]’ that prevents it from being opened or locked.”
- A Write Conflict box saying another user changed the record you’re editing
Common causes
- Someone opened the database in Exclusive mode, locking everyone else out
- Someone is making design changes (editing a form, report, or module) in a shared file
- Users don’t have permission to create and delete files in the database folder, so Access can’t manage its lock file
- A leftover lock file (.laccdb or .ldb) from a crash
- Everyone shares one unsplit database file
How to fix it
- Check the default open mode. In Access, go to File > Options > Client Settings and make sure Default open mode is set to Shared.
- Find who has it open. The lock file in the database folder can show which computer is connected. Ask that user to close Access.
- Clear a stale lock file. Once nobody is using the database, delete the .laccdb file in the same folder.
- Fix folder permissions. Every user needs Modify permission (read, write, create, delete) on the folder that holds the database, not just the file.
- Split the database. Put the tables in a back-end file on the network, and give each user their own copy of the front-end (forms, queries, reports, code) on their computer. Design changes then happen in the front-end without locking anyone out.
- Turn on record-level locking. In File > Options > Client Settings, check Open databases by using record-level locking.
Still locking up?
If your team has outgrown what a shared Access file can handle, we can help with a split, a SQL Server back-end, or a full move to Power Platform. Book a free diagnostic or see our Access Maintenance & Support service.