Fix Multiuser Locking Errors in Microsoft Access 2016
Question details
The user needs multiple Access front ends to open and use the same back-end database simultaneously.

- Product
- Microsoft Access 2016
- Device & OS
- Windows 10
- Scenario
- A single user runs multiple front ends on one computer, with each front end performing a different task against the same back-end database.
- Observed behavior
- Access reports that the Admin user has placed the database in a state that prevents it from being opened or locked.
Identify the back-end file and the folder containing it, then close all Access front ends before checking settings or lock files. Confirm that your Windows account can read, write, create, and delete files in that folder.
Configure the Access back end for shared use
Check folder permissions, linked tables, and locking settings when multiple front ends need the same database.
A shared network folder is not required when all front ends run on the same computer. If the back end is on a network share, use a consistent UNC path and ensure each user has the required folder permissions.
In File Explorer, right-click the folder containing the back-end database and select Properties > Security. Confirm that the account running Access can read, write, create, and delete files there; ask your administrator to adjust permissions if needed.
Open each front end and use External Data > Linked Table Manager to check the links to the back-end tables. Keep forms, queries, reports, and VBA in separate local front-end copies. For a network share, relink using a UNC path such as \\server\share\database.accdb.
In each front end, open File > Options > Client Settings and find the Advanced section. Set Default open mode to Shared, review Default record locking, and avoid opening the back end with Open Exclusive.
Open a form in Design view, display its Property Sheet, and check Record Locks. Choose No Locks or Edited Record as appropriate for the task, rather than locking all records unnecessarily.
Close Access, reopen the front ends normally, and try using the linked tables at the same time. Avoid Design view or operations that require exclusive access while testing.

Investigate a stale lock file or database corruption
Use these checks if the error continues after permissions and shared-open settings have been verified.
Use WPS Office for documents and exported database data
WPS Office is a free, lightweight alternative for everyday documents and spreadsheets, with a familiar interface that makes moving Office files straightforward. It does not resolve Access locking errors or replace an Access database, but it can help you review data exported to a supported spreadsheet format.

Frequently Asked Questions
Do I need a shared network folder for multiple front ends on one computer?
No. A local folder can work when all front ends run on the same computer. The account running Access still needs permission to read, write, create, and delete files in the back-end folder.
Why does Access need to create a lock file?
Access uses a lock file, typically .laccdb for an .accdb database, to coordinate shared access. The account needs appropriate permissions in the folder containing the database, not just permission to read the database file.
Where do I change the default open mode in Access 2016?
Open File > Options > Client Settings and find the Advanced section. Set Default open mode to Shared, then close and reopen Access before testing.
Can I delete an Access lock file while someone is using the database?
No. Close all Access sessions and verify that no process still has the database open before removing a lock file that remains in the back-end folder.
Can WPS Office fix this Access database error?
No. The error must be addressed in Access or its database environment. WPS Spreadsheets can work with data exported to a supported format such as XLSX, but it does not replace the Access database.




