The creation and customization of database applications using Microsoft Access
The behavior matches a known issue with Access databases on network file shares that became common after certain Windows and Office updates, especially with split databases used by multiple users.
For a split database on a network share, apply the supported workaround on the file server that hosts the back-end .accdb:
- On the server that stores the back-end database, sign in with an account that has local administrator rights.
- Open an elevated Command Prompt:
- Select Windows Start, type Command.
- Right‑click Command Prompt and choose Run as administrator.
- Run these commands exactly as shown to disable SMB leasing for the server service:
This change is required only on the machine hosting the shared back-end database, not on each client.REG ADD HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters /v DisableLeasing /t REG_DWORD /d 1 /f NET STOP SERVER NET START SERVER - Ensure all client machines running Access are fully updated to the latest Office build, as the fix for related network‑share issues may not be applied automatically. Follow the steps in Install Office updates on every machine that uses Access.
Additional points:
- The error is triggered by specific usage patterns of the Access Database Engine with networked files and simultaneous multi‑user access; disabling leasing on the server mitigates this.
- Continuing to use the database in this state can increase the risk of corruption. Maintain regular backups and continue to use Compact and Repair as needed, but rely on the server‑side leasing workaround and Office updates to address the root cause.
References: