Fix an Unrecognized Database Format Error in Shared Microsoft Access Databases
Question details
Resolve intermittent unrecognized database format errors in a shared Microsoft Access database.

- Product
- Microsoft Access for Microsoft 365
- Device & OS
- Windows Server 2012 for the shared database host; client OS not provided
- Scenario
- Multiple users access shared data through separate Access front ends hosted on a server.
- Observed behavior
- The shared data file intermittently triggers an unrecognized database format error. Compact and Repair restores access temporarily, but the error returns.
Identify the shared back-end file and confirm where each user's front end is stored. Record the Access version and build on each workstation, and arrange a maintenance window when all users can disconnect.
Check the Multi-User Setup, Network, and Access Builds
Use this approach to investigate recurring errors that Compact and Repair only temporarily resolves.
In each front end, open External Data > Linked Table Manager and check that the linked data tables point to the shared back-end file.
Place a separate front-end copy on each user's computer rather than running those copies from the server. Update their linked table paths to the shared back end if necessary.
Use File Explorer to confirm that the back end is on a reliable shared network location, not in a synchronized folder. Investigate network disconnects and use wired connections where practical.
In Access, open File > Account > About Access on each workstation to record its version and build. Check File > Account > Update Options and review Microsoft's known issues and workarounds for the installed build before applying updates.
Confirm that the database format is compatible with every user's Access version. Check Microsoft's support documentation for the Access builds, client Windows versions, and Windows Server 2012 host.

Compact and Repair the Shared Access Back End
Use Compact and Repair during a maintenance window to attempt to recover the shared file after an error.
Use WPS Office for Everyday Spreadsheet and Document Work
WPS Office is a free, lightweight alternative with a familiar interface and support for common Microsoft Office formats, making it easier to move everyday documents and spreadsheets. It does not repair or run Microsoft Access databases.

Frequently Asked Questions
Why does the error return after Compact and Repair?
Repair may restore the file without resolving network interruptions, an Access build issue, or a multi-user configuration problem. Check the shared location, local front ends, and Access builds.
Can users keep their front ends on the server?
For a shared Access database, place a separate front-end copy on each user's computer and keep only the back-end tables on the shared network location. Check the table links under External Data > Linked Table Manager.
Do all users need to disconnect before repairing the back end?
Yes. Have everyone close their front ends and confirm that no process has the back-end file open before selecting Database Tools > Compact and Repair Database.
Where can I find my Access version and build?
In Access, open File > Account > About Access. Compare the recorded versions and builds across workstations and check Microsoft's known issues for those builds.
Can WPS Office repair an Access database?
No. WPS Office does not repair or run Access databases. It can work with spreadsheet data exported from Access, such as an XLSX file.




