Expert guide
Access Database Opens Read-Only: Causes and Fixes
Start with the lock file and folder permissions; that fixes most cases
Call us at +1 (385) 386-3860
Short answer: Access opens a database read-only when it cannot create or update its lock file (.laccdb) in the database's folder. Give every user Modify (not just Read) permission on the folder, clear the file's Read-only attribute, make sure you are opening the real file rather than an email, ZIP or temporary copy, and check nobody has it open exclusively. Never run a shared back end from OneDrive or Dropbox. If it is still read-only, our Access support team can look with you.
A yellow bar saying "Read-Only: this database has been opened read-only", or edits silently refusing to save, usually starts after a server move, a new user, or someone copying the database to a new folder. The database itself is fine. Access simply cannot do the housekeeping it needs to let several people write safely, and that housekeeping happens in the folder, not the file.
Cause 1: Folder Permissions and the Lock File
When you open Database.accdb, Access creates Database.laccdb (or .ldb for .mdb files) in the same folder. It writes each user's machine name into it and deletes it when the last user leaves. To do that, every user needs to create, modify and delete files in the folder.
Right-click the folder → Properties → Security. Users (or their group) need Modify, which includes create and delete.
Share permissions on the network share also apply; the effective permission is the more restrictive of share and folder.
Test: as the affected user, try creating and deleting a text file in that folder. If you cannot, Access cannot either.
This is the cause in the large majority of read-only cases we see, particularly after IT moves the database to a new server and copies file permissions but not folder permissions.
Cause 2: The File's Read-Only Attribute
Right-click the .accdb → Properties → General. If Read-only is ticked, untick it. Files copied from a CD, restored from some backup tools, or extracted from certain archives can carry the attribute.
Cause 3: You Are Opening a Copy
| Where it was opened from | What happens | Fix |
|---|---|---|
| Email attachment | Opened from a temporary, read-only folder | Save it to a proper folder first |
| Inside a ZIP file | Windows shows the file but it is not really extracted | Extract all, then open |
| Browser download | May be marked as from the internet and blocked | Unblock in file properties; save to a trusted location |
| Old desktop shortcut | Points to an outdated or archived copy | Recreate the shortcut to the current front end |
Cause 4: Exclusive Mode
If anyone opens the database with Open Exclusive (from the Open dialog's dropdown, or a shortcut with the /excl switch), nobody else can open it for writing. Also check File → Options → Client Settings → Default open mode: it should be Shared for multi-user databases.
Cause 5: Read-Only Network Shares and Media
The share itself is configured read-only for some groups.
A mapped drive letter on one PC points to a different, read-only path.
The file sits on a DVD, a read-only USB stick, or a snapshot or backup volume.
Compare the full UNC path (\\server\share\folder\file.accdb) on a working PC and a failing one. Different drive mappings are a classic cause of "it only happens to Sarah".
Cause 6: Sync Folders (OneDrive, Dropbox, SharePoint)
Sync clients replace files and hold their own locks while uploading. Access sees the file change underneath it, may fall back to read-only, and multi-user use leads to conflicts and corruption. Access back ends belong on a local disk for single users or a regular Windows file share for teams; for remote access, use remote desktop or move the data to SQL Server.
The risks of shared files over unreliable connections are covered in Access corruption over LAN, Wi-Fi and VPN.
Cause 7: Leftover Lock File After a Crash
If Access crashed, a .laccdb may remain. Usually Access reuses it, but if the file is locked by a server process or has odd permissions, delete it once you are certain nobody is in the database. Repeated crashes that leave lock files are a sign of network or corruption problems worth investigating.
Cause 8: The Database Is Damaged
Occasionally Access opens a damaged file read-only or refuses to save. If permissions and location are fine and the problem persists, make a copy and try Compact and Repair on the copy. If that fails, see Access database repair or compact and repair not working.
Five-Minute Checklist
Can the user create and delete a file in the database folder? If not, fix folder permissions.
Is the file's Read-only attribute ticked?
Is it the real file on the server, not an email, ZIP, download or synced copy?
Is anyone else in exclusive mode? Is default open mode Shared?
Is the path identical to a PC where it works?
A properly split database also helps: each user opens their own front end, and only the back end needs shared write access. See how to split an Access database.
FAQ
Read-only Access database FAQ
Lock files, permissions and locations