1. Triage the original
We confirm whether this is a version issue or real corruption, and where the damage sits. That decides everything else, and it costs you nothing.
Access recovery
Access Says “Unrecognized Database Format” and the File Will Not Open
The error has two completely different causes, and the wrong first move can cost you records. Here is how to tell them apart, what to do in the next ten minutes, and how recovery works.
File will not open and the team is stopped? Call +1 385 386 3860 before anything else rewrites the file.
- Recovery rateMost records recoverable when the original is untouched
- AssessmentFree, and usually same business day
- HandlingWe work on copies, never your original
Access shows the message, the file stays shut, and nobody can work. Before touching anything else, make a copy of the file and put it somewhere safe. Almost every unrecoverable case we are sent became unrecoverable after the original was rewritten by a repair attempt, not from the original damage.
The error has two causes, and they need opposite responses
Cause 1: a version mismatch, which is not damage at all
If the file was created or saved by a newer build of Access than the one opening it, Access reports the same unrecognized format message even though the file is perfectly healthy. This is common after one person upgrades Microsoft 365 ahead of everyone else, or when a file arrives from a client on a newer version. The fix is to open it in the newer version and save it back to a compatible format. No recovery work is needed, and running a repair tool on it can introduce real damage to a file that had none.
Cause 2: the internal structure was damaged during a write
Access writes changes directly into the file. If that write is cut off partway through - a dropped network connection, a laptop going to sleep, a power cut, a VPN timeout - the structure describing where objects live can be left inconsistent. Access reads the header, finds something it cannot interpret, and refuses to open rather than risk making it worse. The records themselves are usually still in the file.
What to do in the next ten minutes
Stop everyone from opening the file. Each attempt can write to it.
Copy the file to a different folder, ideally a local drive, and label the copy clearly. Work only on copies from now on.
Find your most recent backup, even if it is a few days old, and copy that somewhere safe too. It is your fallback.
Check whether anyone upgraded Office recently. If one person is on a newer build, try opening the file there before assuming corruption.
Note what was happening when it broke: who was in it, whether they were on Wi-Fi or VPN, whether a machine crashed. That narrows diagnosis considerably.
What not to do
Do not run Compact and Repair on your only copy. It rewrites the file in place and can fail partway through.
Do not run a series of third-party repair tools hoping one works. Most save output over the source, and each pass reduces what a specialist can recover.
Do not delete the damaged original once you have a partial recovery. Later passes often get more out of it.
Do not keep working in a recovered copy on the same network share that broke it. You will be back here.
How we recover the file
Our recovery sequence
Diagnosis before intervention, always on copies.
2. Extract at table level
Rather than repairing in place, we read the tables directly out of the damaged file so the data is secured before any rebuilding starts.
3. Rebuild the structure
Tables, relationships, queries, forms, reports and VBA are rebuilt into a clean database, so you are not left with a fragile file that fails again next week.
4. Verify against something real
We reconcile record counts and check the figures your team recognises - last month's totals, open orders, current stock - so you know what came back.
5. Fix the cause
A recovered file on the same setup will corrupt again. We split the database properly, move front ends to each desktop, and tell you plainly if the data belongs on SQL Server.
Work is performed on backup copies only - secure handling, nothing shared with third parties.
When the data is recoverable, and when it is not
If the damage sits in the objects around the data - the catalogue, forms, queries, the VBA project - the records normally come back in full. If it landed inside the data pages themselves, some rows in the affected tables can be unreadable, and honest recovery means telling you which tables and roughly how many rows rather than quietly delivering a file with gaps. The single biggest factor is not the severity of the original corruption; it is how many times the file has been rewritten since. An untouched original is the best thing you can give us.
What it costs
Fixed-scope project estimates based on the business value we deliver. Projects typically start at $1,200 - smaller fixes can be less, larger systems more.
The assessment is free, and you get the figure in writing before any billable work starts. If the honest answer is that your file only needs opening in a newer version of Access, we will tell you that and there is nothing to pay. For the wider picture on pricing, see Access database repair or talk to a Microsoft Access consultant.
Stopping it happening again
Nearly every file we recover comes from the same setup: one database file on a share, opened directly by several people, at least one of them over Wi-Fi or VPN. The database should be split, with a front end copied to each desktop and only the data on the server. If more than a handful of people work in it at once, or anyone connects remotely, the data belongs in SQL Server with Access kept as the screens - see Access to SQL Server migration. For why remote connections cause this, read Access corruption over LAN, Wi-Fi and VPN.
FAQ
Frequently Asked Questions
Find answers to common questions about our services
It means Access opened the file, read the header, and could not make sense of the structure it found. There are two very different reasons for that. Either the file was written by a newer version of Access than the one you are opening it with, which is a version problem and not damage, or the internal structure has been damaged partway through a write, which is real corruption. The error text is identical in both cases, which is why guessing is expensive.
In most cases the records are still physically in the file. Access refuses to open it because the structure that describes where the records live has been damaged, not because the records were deleted. Recovery works by reading the tables directly and rebuilding the surrounding structure. How much comes back depends on whether the damage landed in the data pages or only in the objects around them.
Not on your only copy. Compact and Repair rewrites the file in place, and if it fails partway through you can be left with less than you started with. Make a copy first and work on the copy. If you have already run it and things got worse, stop and send us the original file if you still have it, plus any backup from before the repair attempt.
Often yes, but the odds drop each time a tool rewrites the file. Third-party repair utilities frequently save their output over the source. If you have an untouched copy or an older backup, send that as well, even if it is a few days old. A slightly stale file in good condition is usually worth more than a current file that four tools have rewritten.
We quote a fixed price for a defined piece of work rather than billing hourly. Fixed-scope project estimates based on the business value we deliver. Projects typically start at $1,200 - smaller fixes can be less, larger systems more. For a file that will not open, the first step is a free assessment: we tell you what is recoverable before you commit to anything. Projects typically start at $1,200, and urgent cases are usually looked at the same business day.
The most common cause we see is a write interrupted by the network: a shared database on a file server or NAS, accessed over Wi-Fi or VPN, where a laptop dropped its connection mid-transaction. Other causes are an unsplit database shared by several people, a workstation losing power with the file open, and a front end left on a network share instead of copied to each desktop.
Need this file open again?
Send us the details and your most recent backup. We will tell you what is recoverable before you commit to anything.
1
15-min audit
→
2
Fixed-scope quote
→
3
Deliver outcome
20+Years Experience
500+Projects Delivered
FixedScope Quotes
1 HourResponse Time
Prefer to talk? Call us at +1 385 386 3860