Access Evolved
Phoenix, AZ · Remote across the US · Same-day triage
Microsoft Access database fix and repair
A repair tool can open your file tonight. It cannot tell you why it broke, and whatever broke it is still running.
Anthony PasseriMBA
21+ years on Access · Power Platform certified Buckeye, AZ 85396 · Reviewed 24 September 2026What’s wrong with your Access database?
Pick the one that matches what you’re seeing. You get the first move free, whether you call or not.
What does “Unrecognized database format” mean?
Get everyone out and copy the file. Do not run Compact and Repair on your only copy.
The header of the file is damaged, or the file was written by a newer version of Access than the one opening it. It usually looks worse than it is.
An interrupted write, often a dropped network connection or a machine that slept mid-save. Occasionally a version mismatch after an Office update.
Rarely. Records are usually intact and can be extracted into a clean container.
Recover to a clean database, reconcile record counts, then remove whatever interrupted the write.
Why does Access say the database is in an inconsistent state?
Everyone out, copy the file, and stop the cycle of repair-and-carry-on.
This one is not your fault, and it’s worth knowing that before anyone sells you a rebuild. Microsoft publishes an article on databases reported in an inconsistent state on network shares.
How the Access database engine uses networked files under modern Windows. Microsoft’s documented remedy is still a workaround rather than a fix.
Disable leasing on the machine hosting the back end. In a split database only the host needs the change.
Split the database properly, or move the tables to SQL Server with Microsoft’s free SSMA tool and keep your existing forms.
Why can’t Access lock the file?
Check whether the folder is read-only for the person seeing it, and whether a stale lock file is sitting next to the database.
Access writes a small lock file next to the database so several people can work at once. When it can’t create or read that file, everything stops.
Share permissions, a user without write access to the folder, or a session that died without releasing the lock.
No. This is an access problem, not a corruption problem.
Permissions corrected, and then the underlying question: why is everyone opening one file rather than their own front end?
Why is my Access database so slow?
Find out whether you have one file or two. If it’s one, you have your answer.
Nine times in ten, the database has never been split. Microsoft caps an Access database at 2 GB and 255 concurrent users, and an unsplit file on a share hits trouble long before either. Everyone opens one file on a share, so every form drags whole tables across the network, and it degrades as you add people.
Missing indexes, queries pulling entire tables, a back end approaching Microsoft’s 2 GB ceiling, or Wi-Fi between the user and the file.
No, but an unsplit database on a share is also the highest corruption risk you can run.
Split it: tables in one back end on the server, a copy of the front end on each machine. Usually a day.
Why does Access crash on one specific form?
Write down the exact steps that trigger it. Reproducible beats intermittent every time.
When the failure is reproducible and local to one object, the damage is usually local too. That is good news.
A corrupted form or VBA module, a broken reference after an Office update, or a query returning something the form can’t render.
Almost never. The object is damaged, not the records behind it.
Rebuild the affected object and repair the reference. Often done inside a single session.
Nobody has the database password. Can we get in?
Confirm who in your business can authorize the work in writing.
The usual version of this: the employee who set a VBA project password left in 2014 and nobody wrote it down. The business owns the database and can’t get into its own design.
A database your business owns, and written authorization from someone entitled to give it. We don’t work on files whose ownership is unclear.
No. The data is usually reachable even when the design is locked.
Regain design access, then document the thing properly so this can never happen to you twice.
Seeing something else? These six cover most of it, not all of it. Describe what you’re looking at and you get the same answer, free. 623-267-5720 →
Whichever one you picked, there is a second question underneath it, and it is the one that actually decides what this costs you: why did it happen at all?
The file opens again. That is not the same as being fixed.
Three of these four steps announce themselves. The one that costs you money does not.
Repair completed successfully
The tool puts the records back. It has no way of telling you what interrupted the write in the first place.
The tool opens it
You download something for $79, point it at the file, and get your data back. Real relief. Everyone goes home.
It feels slow
Forms take a beat longer. Someone blames the network, or the new laptop, or Windows updates. Nobody writes it down.
The same error
Different table this time. You run the tool again. It works again. The cycle is now normal and nobody questions it.
A record doesn’t save
No error, no dialog, no warning. An invoice, a work order, a patient note. You find out at quarter end, from a customer.
Steps one through three are cheap. Step four is the one that costs money, and it is the only one a repair tool cannot prevent. Which raises the obvious question.
Why Access databases corrupt, and why it is almost never something you did
Three things cause nearly all of it, and all three are in this room. Not one of them is the file.
“Usage patterns in the Access Database Engine with networked files that did not cause issues with previous versions of Windows, but no longer work properly.”
“We have not been able to fully deploy the fix due to new issues that occur only when the fix is present.”
Microsoft Support · Access reports that databases are in an inconsistent state
Read that second sentence again. The documented remedy is still a workaround, disabling leasing on the machine that hosts the back end, and it has been for years. If you have been quietly assuming somebody on your team did something wrong, you can stop.
A repair tool operates on the file. Every cause on this page lives outside the file, which is why the tool keeps working and the problem keeps coming back.
Access database repair software, and what it cannot do
Repair software is genuinely useful, and if your file is a one-off casualty of a power cut, buy it and save your money. Here is the honest comparison.
If your file is a one-off casualty and you have a good backup, buy the tool. If it has happened twice, you do not have a file problem. Here is what we actually do.
How we repair a corrupt Access database
Three moves, in this order, every time. The order is the part that matters.
Stop the bleeding
Everyone out of the database. A byte-for-byte copy taken before anything is attempted, and all work done on the copy. Repair attempts on the only file in existence are how recoverable situations stop being recoverable.
How do we know the data came back whole?
Data extracted into a clean container, then reconciled. We count records against reports you already trust, so "recovered" is a number you can check rather than a word we used.
How do we stop it happening again?
Split the database, fix the host, or move the tables to SQL Server with Microsoft's free migration tool while your staff keep the forms they already know. Whichever one the evidence points at, written down so the next person inherits knowledge instead of a mystery.
What you have when we're done
- A database that opens. Reconciled against reports you already trust, so you can check our work rather than take our word.
- A written account of what broke it. Plain English, with the evidence, so you can hand it to your IT provider or your insurer.
- The cause gone, not just the symptom. Split, rehosted, or moved. Whatever your evidence pointed at.
- A backup you have watched restore. Most businesses have never seen theirs tested. You will have.
One person does the work. Here is who.
No account manager, no intake team, and no handoff to somebody you never meet. The person on the diagnostic call is the person who opens your database.
Anthony Passeri, MBA
Pick a time. Bring the database.
Thirty minutes with Anthony on the real file, at no charge. You come away knowing what broke, whether your data is intact, and what it takes to stop it happening again.
You will be talking to the person who does the work, not a scheduler and not a sales team.
Before the call: get everyone out of the database, copy the file somewhere else, and do not run Compact and Repair on the only copy you have. That is free advice whether you book or not.
Loading Anthony’s calendar… or open it in a new tab.
info@azaccessrepair.com · Buckeye, AZ 85396 · Remote across the US