Fix Microsoft Access Cannot Open Databases on Network Drives
Question details
Users are unable to open Microsoft Access databases (MDB or ACCDB files) stored on network drives, often encountering read-only warnings or lock file errors.

- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Attempting to access, read, or write to a shared Access database hosted on a local area network (LAN) drive.
- Observed behavior
- The database fails to open, returns "Could not lock file" error messages, or opens strictly in read-only mode, completely blocking multi-user functionality.
Ensure you have a stable connection to your company network or VPN, and test opening a reliable local copy of the database to verify that the file itself is not corrupted.
Verify Network Folder and Share Permissions
The most common cause of network drive database errors is insufficient permissions to create, modify, or delete the Access lock file (.laccdb or .ldb).
Microsoft Access requires full read, write, and delete permissions in the folder where the database resides to properly manage the lock file. Without these permissions, Access cannot manage concurrent users and will throw lock errors.
Using Windows File Explorer, right-click the network folder containing the database and select 'Properties'.
Navigate to the 'Security' tab and verify that your user account or user group has 'Modify', 'Read & execute', 'List folder contents', 'Read', and 'Write' permissions enabled.
Go to the 'Sharing' tab, click 'Advanced Sharing', then 'Permissions' to ensure share-level permissions also allow Full Control or Change access.
If you cannot change these settings yourself due to administrative restrictions, contact your IT team to request the necessary read/write/delete permissions for the database directory.

Review Antivirus and Network Security Rules
Aggressive antivirus software or strict network security policies can incorrectly flag and block Microsoft Access from modifying files over a network connection.
Looking for a lighter, faster alternative for your daily office tasks?
While complex database management requires specialized tools like Microsoft Access, handling everyday spreadsheets, documents, and presentations shouldn't be a hassle. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office for all your essential data analysis and document creation needs.
- 1. Download WPS Office: Visit the official WPS Office website to download the free installation package.
- 2. Install the Application: Run the installer and follow the fast, straightforward on-screen instructions to set up the software.
- 3. Open Your Files: Launch WPS Office and directly open your existing Microsoft Office files without losing your formatting or formulas.

Frequently Asked Questions
Is there a Microsoft policy that prevents Access from opening databases on a network drive?
No, there is no general Microsoft policy blocking MDB or ACCDB files from functioning on network drives. If a database is blocked, the issue is almost always related to your local network configurations, active folder permission settings, or third-party antivirus rules.
Why do I get a "Could not lock file" error when opening an Access database?
This error occurs when Microsoft Access lacks the necessary folder permissions to create or modify the temporary lock file (.laccdb or .ldb) required for multi-user database access. Users must have read, write, and delete permissions assigned to the network folder.
Will adding the network drive to Access Trusted Locations fix the issue?
Adding the drive to Trusted Locations resolves issues related to macro execution and active content blocking, but it does not fix underlying read-only errors or lock file creation failures caused by restrictive network folder permissions.
Can I safely run Compact and Repair on a network-shared Access database?
No, you should never perform a Compact and Repair operation directly over a LAN connection. Even a momentary network drop or latency spike during the process can severely and permanently corrupt the database file. Always copy the file to a local drive before repairing.




