If you are reading this because your Access database just stopped working, start here: close every instance of Access that has the file open, make a copy of the file immediately before doing anything else, and do not let anyone else open it until you have that backup. A corrupted Access file can get worse with each failed open attempt, and the copy you make right now may be the most complete version you ever recover.
If you are reading this because you are worried it might happen — because the file has been acting strange, because it is old, because too many people are in it at once — that instinct is correct and this post will tell you what you need to know.
Why Access Databases Corrupt
Access database corruption is not random. It happens for specific, predictable reasons — and understanding those reasons tells you a lot about whether your current setup is at risk.
Network interruptions during a write operation. This is the most common cause of serious Access corruption. When a record is being written to the database and the network connection drops — even for a fraction of a second — the write operation completes incompletely. The file now contains a partial record that Access cannot reconcile. Over time, if this happens repeatedly, the damage accumulates until the database refuses to open.
If your Access file lives on a shared network drive and multiple people open it simultaneously, this risk is present every single day.
Improper closure. Access databases need to be closed cleanly. When a computer crashes, loses power, or gets shut down while Access is open, the file does not get a chance to complete its housekeeping. The result is an inconsistently written file that may open fine a dozen times before the damage manifests as a real problem.
File size limits. Access databases have a maximum file size of two gigabytes. As a database approaches that limit, performance degrades, errors become more frequent, and the risk of corruption increases. Many business owners do not know this limit exists until they hit it.
Too many simultaneous users. Access was not designed for multi-user environments. Microsoft’s own documentation recommends no more than a handful of concurrent users on a single Access file. In practice we see businesses with ten, fifteen, or twenty people opening the same file simultaneously — a setup that creates constant write conflicts and dramatically increases corruption risk.
Outdated Access versions. Older versions of Access have known bugs that can cause corruption under specific conditions. Running Access 2016 or 2019 — both of which lost Microsoft support in October 2025 — means those bugs are not getting fixed.
Virus or ransomware. Malware that targets Office files can corrupt an Access database directly or encrypt it in a way that makes it unrecoverable without paying a ransom. Running unsupported software with unpatched security vulnerabilities increases exposure to exactly this threat.
What Corruption Actually Looks Like
Access corruption does not always announce itself dramatically. Sometimes the database simply refuses to open with a generic error message. But more often it shows up gradually, in ways that are easy to dismiss until something serious happens.
Watch for these warning signs:
The database takes significantly longer to open than it used to. Records that should exist are missing or appear duplicated. Forms that worked yesterday produce errors today. Queries that ran in seconds now time out or return wrong results. Access prompts you to compact and repair more frequently than usual. The file size has grown dramatically without a corresponding increase in records.
Any of these symptoms in isolation might have an innocent explanation. Multiple symptoms together are a signal that the database is under stress and corruption may already be present or developing.
What Recovery Options Look Like
If your database is already corrupted, you have a few options — none of which are guaranteed, and all of which are more limited than most people hope.
Access Compact and Repair. This is the built-in recovery tool and the right first thing to try. Go to Database Tools and select Compact and Repair Database. This works well for minor corruption — fragmented records, inconsistent indexes, minor write errors. It does not work for serious structural damage.
Opening in exclusive mode. Sometimes a database that will not open normally can be opened in exclusive mode — hold Shift while opening, or use the Open dialog and select Open Exclusive. This prevents other users from accessing the file during the repair attempt and sometimes allows Access to complete a recovery it could not do with the file in shared mode.
Importing objects into a new database. If the file opens but behaves incorrectly, create a new blank Access database and use the Import function to pull tables, queries, forms, and reports from the damaged file one object at a time. Objects that import successfully are recovered. Objects that fail to import are the ones with serious damage.
Restoring from backup. If you have a recent backup — a copy of the file from yesterday, last week, a previous version in OneDrive version history — restoring from backup is often the fastest and most complete recovery path. The question is how recent the backup is and how much data you are willing to lose.
Third-party recovery tools. Tools like DataNumen Access Repair and AccessFIX can sometimes recover data from databases that Access itself cannot open. They are not free and they are not guaranteed, but for a database containing critical business data they are worth trying before declaring the data unrecoverable.
Professional data recovery. For severe corruption where all other options have failed, professional data recovery services can sometimes extract data directly from the file at a binary level. This is expensive — typically several hundred to several thousand dollars — and the outcome is not certain.
The honest truth about Access corruption recovery is that the further along the damage is, the less you get back. Recovery is almost always partial. Data entered since the last clean backup is frequently unrecoverable. The best outcome from a serious corruption event is getting most of your data back and losing some. The worst outcome is losing everything.
The Deeper Problem Corruption Reveals
If your Access database just corrupted — or if you are worried it might — the corruption itself is not really the problem. It is a symptom.
The underlying problem is that your business is running a critical process on a platform that was not designed to be business-critical infrastructure. Access is a desktop database tool. It was built for individual use, for moderate data volumes, for low-concurrency environments. When businesses use it as their operational backbone — with multiple users, mission-critical data, and no redundancy — they are asking it to do something it was not designed to do.
The corruption risk is one expression of that mismatch. The single-point-of-failure risk is another. The key-person dependency is another. The lack of audit trail, the absence of role-based security, the inability to access data from a mobile device — all of these are expressions of the same underlying issue.
Recovering from corruption and going back to the same Access setup is like patching a tire that has been run flat for ten miles. You might get a little more time out of it. But the underlying damage has been done, and the next failure is a matter of when, not if.
What the Right Long-Term Solution Looks Like
For businesses whose Access database has corrupted — or whose database is showing the warning signs — the right conversation is not just about recovery. It is about what comes next.
The process your Access database supports needs to move to a platform that was designed for what you are actually using it for: multi-user access, cloud storage, role-based security, automatic backups, and a data structure that does not live in a single file on a shared network drive.
For most small businesses already in the Microsoft ecosystem, that means Power Apps as the front end and Dataverse or SQL Server as the backend. The data lives in the cloud, not in a file. Multiple users can work simultaneously without write conflicts. Backups happen automatically. There is no file to corrupt because there is no file — there is a database managed by Microsoft’s cloud infrastructure with enterprise-grade redundancy built in.
The migration process starts with recovering whatever data can be recovered from the Access file, cleaning and mapping it to the new data structure, building the replacement application, and retiring the Access dependency entirely. For a mid-complexity Access database, that process typically takes four to eight weeks.
What to Do Right Now
If your database corrupted today, work through the recovery options above in order — Compact and Repair first, then exclusive mode, then object import, then backup restore, then third-party tools.
If your database is showing warning signs but has not fully failed yet, do three things immediately. Make a backup copy of the file today and store it somewhere separate from the original — not on the same network drive, not on the same machine. Document your recovery options so you know exactly what to do if the file fails tomorrow. And start a conversation about migration, because the window to do this on your own terms rather than in crisis mode is open right now and will not stay open indefinitely.
If your database is fine today but you recognize the risk profile — multiple users, network drive, old Access version, no formal backup process — do not wait for the warning signs. The businesses that migrate before something breaks pay a fraction of what the businesses that migrate after something breaks pay. The data is intact, the timeline is controlled, and nobody has to explain to a client why their records are unavailable.
The Bottom Line
Access database corruption is not bad luck. It is the predictable outcome of asking a desktop tool to do the work of a cloud database over a long enough period. The risk is manageable in the short term and inevitable over a long enough timeline.
The businesses that come through it well are the ones that use it as the forcing function it is — to finally make the move to a platform that was actually designed for what they need it to do.
Ready to talk through your options? Reach out to Anthony at AccessEvolved — email anthony@accessevolved.com or call 212-951-1010. No sales pitch, just a straight conversation about what makes sense for your situation.