Permission & Access Issues

Fix Microsoft Access Error 3073 and a Backend File in Use

Algirdas JasaitisAlgirdas Jasaitis Nov 14, 2026 869 views

Question details

The user needs to resolve Access Error 3073 and regain exclusive access to a shared backend for editing and compacting.

Fix Microsoft Access Error 3073 and a Backend File in Use
Product
Microsoft Access
Device & OS
not provided
Scenario
A split database has a shared backend and separate front-end files.
Observed behavior
After Error 3073, Access reports that the backend file is in use, although no active users are visible, preventing editing and compacting.
Before you start

Identify the shared backend file and its folder, and ask all users to close their front-end databases and Access sessions. You may need a server administrator to check open-file sessions and shared-folder permissions.

Solution 1Recommended

Clear a stale backend lock and compact the database

Use this method when Access reports that the shared backend is in use and you cannot compact it.

1
Close all Access sessions

Ask every user to close the front-end database and exit Access. Close any Access window or process on your own computer that may have the backend open.

2
Check server open files

If the backend is on a Windows server, ask an administrator to check Computer Management > Shared Folders > Open Files for sessions using the backend. Have the owner close any active session before proceeding.

3
Remove a leftover lock file

Open the backend folder and look for a lock file with the same base name as the database: .laccdb for an .accdb backend or .ldb for an .mdb backend. Only after confirming that no users or processes have the database open, delete the leftover lock file if it remains. Do not delete the database file.

4
Open the backend exclusively

In Access, choose File > Open, browse to the backend, select it, and use the arrow beside Open to choose Open Exclusive.

5
Compact and repair

With the backend open exclusively, choose File > Info > Compact & Repair Database. If Access still reports that the file is in use, recheck server sessions and folder permissions.

Clear a stale backend lock and compact the database
Keep interface objects in the front end: Forms, queries, and other user-interface objects should normally be stored in each front end, while shared data tables remain in the backend.
Free Microsoft Office alternative

Use WPS Office for Spreadsheet Work Alongside Access

WPS Office is a free, lightweight alternative for everyday document and spreadsheet work, with a familiar interface and Microsoft Office format compatibility for easier migration. It does not repair Access databases or replace an Access backend.

Work with tabular data in WPS SpreadsheetsOpen and save Microsoft Excel XLSX and XLS filesUse a familiar interface for everyday office tasksMove existing Office documents into a lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Can I delete the Access lock file while someone is connected?

No. First confirm that all users and processes have closed the database. Then delete the matching .laccdb or .ldb file only if it remains in the backend folder.

Why does Access still say the backend is in use?

A front-end session, another Access process, or a server open-file session may still hold the backend. Ask an administrator to check Computer Management > Shared Folders > Open Files and have active users close their sessions.

Does deleting the lock file fix Error 3073?

Not necessarily. Error 3073 may result from a non-updateable query, a read-only data source, or insufficient permissions. Open the query in Design View and check its underlying tables and permissions.

Where should forms and queries be stored in a split database?

Forms, queries, and other interface objects should normally be in each user's front end. The shared backend typically contains the data tables.