You open a Microsoft Access database and get hit with Error 3343: Unrecognized database format. The file was working yesterday — or maybe it was handed to you by a colleague — and now Access refuses to open it. This error means Access cannot read the internal structure of the file, and there are several specific reasons why.
This guide walks through every common cause of Error 3343, gives you four proven fixes ranked from simplest to most thorough, and explains how to prevent it from happening again.
Error 3343 is the Jet/ACE database engine's way of saying: "I tried to open this file, but the internal format doesn't match anything I know how to read." It is not a generic file-not-found error. Access can see the file, it can access the file on disk, but the bytes inside don't match the expected database structure.
This happens for one of four reasons: a version mismatch between the file format and the Access engine trying to read it, file corruption that has damaged the internal structure, a wrong file extension that misleads Access about the format, or a network path issue that delivers incomplete or garbled data.
This is the most common trigger. The .mdb file format has gone through several internal revisions:
| Access Version | Jet Engine | Internal .mdb Format |
|---|---|---|
| Access 97 | Jet 3.5 | Jet 3.x format |
| Access 2000 / 2002 / 2003 | Jet 4.0 | Jet 4.x format |
| Access 2007+ | ACE 12.0+ | .accdb (new format) |
Here's the problem: Access 2013 and later editions use the ACE database engine, which has limited backward compatibility with older Jet 3.x format databases. If you have an .mdb file originally created in Access 97, modern Access may not be able to open it directly. The ACE engine sees the Jet 3.x internal structure and throws Error 3343 because it only fully supports Jet 4.0 and later formats.
Even .mdb files from Access 2000/2002 can occasionally trigger this error if the file was created with certain Jet 4.0 service pack variations that the ACE engine doesn't handle cleanly.
If the database was working fine in the same version of Access and suddenly throws Error 3343, corruption is the most likely cause. Access databases — especially .mdb files — are prone to corruption from:
Corruption damages the internal page structure of the database file. Even a few corrupted bytes in the header can make the entire file unrecognizable to the database engine.
This cause is more common than you might expect. Someone renames a file from .accdb to .mdb (or vice versa) thinking the formats are interchangeable. They are not. The .mdb format uses the Jet engine structure, and the .accdb format uses the ACE engine structure. Renaming the extension does not convert the internal format — it just confuses Access about which engine to use when opening the file.
You'll also see this when a file has no extension or a generic extension like .dat or .bak, and someone adds .mdb assuming it's an Access database.
If the database lives on a network share, a mapped drive, or in a SharePoint-synced folder (like OneDrive for Business), the error can appear even when the file itself is perfectly healthy. This happens because:
The quick diagnostic: copy the file to your local desktop and try opening it from there. If it works locally, the problem is the network path, not the file.
If the error is caused by a version mismatch, converting the file to the modern .accdb format resolves it permanently. This is the recommended fix for any .mdb file you plan to keep using.
If you don't have access to an older version of Access, the Microsoft Access Database Engine 2010 Redistributable (32-bit) includes Jet 4.0 compatibility and can sometimes bridge the gap when installed alongside a newer Access version.
If corruption is the suspected cause, the built-in Compact and Repair tool is your first line of defense.
If Compact and Repair fails because Access can't even open the file, skip to Fix 3. If you have a recent backup, restoring from backup is always more reliable than repairing a corrupted file.
When the file is too corrupted for Compact and Repair but not completely destroyed, you can often salvage most of the data by importing objects into a fresh database.
This method often recovers tables and queries even when forms and VBA modules are damaged beyond repair. Import tables first (the data is the hardest part to recreate), then try forms and reports, then VBA modules last.
If even the import fails, third-party Access recovery tools like Stellar Repair for Access or DataNumen Access Repair can sometimes extract data from severely corrupted files by reading the raw page structure.
If you don't have Access installed and are trying to open the database through another application (a VBA macro in Excel, a .NET application, a Python script using pyodbc), you may need the Access Database Engine Redistributable to provide the necessary drivers.
Note: you cannot install both the 32-bit and 64-bit versions on the same machine. If you have 32-bit Office installed, you must use the 32-bit engine. If you have 64-bit Office, use the 64-bit engine.
Error 3343 is almost always preventable. These practices will save you from encountering it again:
LegacyLift converts .mdb files to .accdb, resolves format compatibility issues automatically, and generates a detailed report of every problem found. No manual version juggling, no guesswork — upload your file and get a working modern database back.
Error 3343: Unrecognized database format comes down to four root causes — version mismatch, file corruption, wrong file extension, or network path issues. The fix depends on the cause: convert the format, repair the file, import into a new database, or install the correct database engine. In every case, the long-term solution is to move away from the legacy .mdb format and onto .accdb, with proper backups and a split database architecture.
If you're managing multiple Access databases across your organization or dealing with files too corrupted for manual repair, our done-for-you service handles the entire migration with a free consultation upfront. Your files are transferred securely and deleted after delivery.