Corrupt Access Database? Fixed-Scope Recovery Before Anything Overwrites It

If the file won't open: what to do first

• Stop everyone from opening the live file. Further opens can make damage worse.

• Make a full copy of the .accdb or .mdb to a local folder you control. Leave the original untouched.

• Do not run Compact and Repair on your only copy. If you try it, use the copy only.

• Note the Access or Office version, how the file is shared (network, VPN, OneDrive), and the exact error text.

• If Compact and Repair already rewrote a damaged file, keep that version and the pre-repair copy if you still have one.

• Send the untouched copy for a free assessment and a fixed-scope recovery quote—do not email passwords in the same message as the file.

• If the database opens but records or forms are missing, treat it as corruption and get a quote before wholesale rebuilds.

Access recovery specialists since 2011 (15+ years). Last updated October 22, 2026. Applies to .accdb and .mdb from Access 97 through Microsoft 365 and Access 2024.

Stop First: Three Things That Turn Recoverable Into Unrecoverable

• Repairing the only copy. Compact and Repair rebuilds the file and can discard whatever it cannot read. Copy the file somewhere safe first, and work on the copy.

• Opening it again and again. Every open attempt, especially by several people, can write to a damaged file. Get everyone out and leave it closed until you have a copy.

• Overwriting a good backup. Restoring over your last good backup, or letting a scheduled job replace it with a damaged file, removes your safety net. Pause the backup rotation until you know the damage date.

Common Access Corruption Errors and What They Mean

Step-by-Step: How to Repair a Corrupt Access Database Yourself

• Copy the damaged file (and, for a split database, the back end) to a safe folder. Use that copy for every step below.

• Make sure no one has the file open, then delete the matching .laccdb (or .ldb for .mdb files) lock file in the same folder. Reopen the copy.

• Try opening with the Shift key held down. This bypasses startup forms and AutoExec macros, which sometimes cause the failure rather than real corruption.

• Run Compact and Repair. Open a blank database in Access, choose Database Tools > Compact and Repair Database, and when prompted select the damaged copy. Save the result under a new name.

• Check for damage that Compact and Repair could not copy: show system objects (right-click the Navigation Pane > Navigation Options > Show System Objects) and look for a table named MSysCompactErrors.

• Create a new blank database, then choose External Data > New Data Source > From Database > Access. Import all tables first, then queries, forms, reports, macros and modules. Whatever fails to import is your damaged object.

• If the problem is VBA code or a database that is bloated or crashes in the editor, run the /decompile command against the copy (see below), then open it, compile (Debug > Compile) and run Compact and Repair again.

• Look for a backup: the most recent verified backup, a previous version of the file (right-click the file > Properties > Previous Versions on a network share), or version history if the file lives in OneDrive or SharePoint.

• If the file still will not open, or data is missing, stop and call for an assessment before any further attempts.

"C:\Program Files\Microsoft Office\root\Office16\MSACCESS.EXE" "C:\Data\MyDatabase_COPY.accdb" /decompile

Salvage Your Tables Without Losing Everything to One Bad Object (VBA)

' Run this from a NEW, blank database (standard module: modSalvage).
' Imports tables from a damaged database one at a time and logs any that fail,
' so you can see exactly which objects are damaged instead of losing everything
' to one bad table. Always point it at a COPY of the damaged file.
' Note: relationships and some table properties are not carried over this way
' and must be recreated afterwards.
Public Sub SalvageTables(ByVal damagedPath As String)
    Dim db As DAO.Database
    Dim tdf As DAO.TableDef
    Dim okCount As Long, failCount As Long
    Dim failed As String

    On Error GoTo OpenFail
    Set db = DBEngine.OpenDatabase(damagedPath, False, True)   ' read-only
    On Error GoTo 0

    For Each tdf In db.TableDefs
        ' Skip system, temp and linked tables
        If Left$(tdf.Name, 4) <> "MSys" And Left$(tdf.Name, 1) <> "~" _
           And Len(tdf.Connect) = 0 Then

            On Error Resume Next
            DoCmd.TransferDatabase acImport, "Microsoft Access", damagedPath, _
                                   acTable, tdf.Name, tdf.Name, False
            If Err.Number = 0 Then
                okCount = okCount + 1
            Else
                failCount = failCount + 1
                failed = failed & tdf.Name & "  (" & Err.Number & ": " & _
                         Err.Description & ")" & vbCrLf
                Err.Clear
            End If
            On Error GoTo 0
        End If
    Next tdf

    db.Close
    Set db = Nothing

    Debug.Print "Imported: " & okCount & "   Failed: " & failCount
    If failCount > 0 Then Debug.Print failed
    Exit Sub

OpenFail:
    Debug.Print "Could not open the damaged file: " & Err.Number & " - " & Err.Description
End Sub

' Usage (Immediate Window, Ctrl+G):
'   SalvageTables "C:\Data\MyDatabase_COPY.accdb"

When to Stop and Call for Professional Recovery

• The file will not open at all, or Access asks to repair it and fails.

• Records are missing or garbled after a Compact and Repair.

• The database holds financial, regulated, patient or customer data you cannot afford to lose.

• Forms, reports or VBA modules are damaged and you do not have an uncorrupted source copy.

• You have already run several repair attempts on the only copy.

• Corruption keeps coming back, which points to a cause that repair alone will not fix.

When Access Fails, Everything Stops, and IT Often Cannot Help

How We Recover Your Database

What's Included in Our Access Database Repair Services

• Free assessment and a written, fixed-scope quote before billable work starts

• Database corruption diagnosis and file recovery, working from copies only

• Table-by-table data recovery and validation against what the file contains

• Rebuilding broken queries, forms, reports and macros

• VBA code repair, decompile and recompile

• Recovery of linked-table and back-end problems in split databases

• Root-cause analysis so the corruption does not return

• Backup planning and a tested restore procedure

• Optimization for stability, once the data is safe

• Documentation of what was done and what to change

Real-World Repair Scenarios

Work performed on backup copies only - secure handling, no data shared with third parties.

Why Access Databases Get Corrupted (and How to Stop It Happening Again)

• A dropped network connection during a write, especially on Wi-Fi or VPN. Access is a file-based database, so a half-finished write goes straight into the file.

• Several users running the same front-end file from a shared folder instead of their own local copy.

• The database sitting in a OneDrive, Dropbox or other synced folder, where the sync client touches the file while Access has it open.

• Antivirus or backup software scanning or copying the file while it is in use.

• A power loss, forced shutdown or crash of a PC with the database open.

• A file near the 2 GB limit, or one that has never been compacted.

• File-server caching and locking settings that misbehave with multi-user Access back ends.

Backups That Would Actually Save You

• Take the copy when nobody is in the database. A backup captured mid-write can inherit the same inconsistency as the original.

• Keep backups somewhere other than the server holding the live file, such as cloud storage or a separate device, so one failure does not take both.

• Keep several generations, not just last night. Corruption is often noticed days after it started, and last night's copy may already contain it.

• Restore one into a test folder on a schedule and open it. That is the only way to know your backups work.

• Write down where backups live and who restores them. A backup nobody can find at 8am is not a backup.

' Standard module: modBackup
' Makes a timestamped copy of a back-end file ONLY when nobody is connected,
' then proves the copy opens. A backup you have never opened is a hypothesis.
Public Function BackupBackend(ByVal srcPath As String, _
                              ByVal backupFolder As String) As Boolean
    Dim lockFile As String, fileName As String
    Dim ext As String, baseName As String, dest As String
    Dim testDb As DAO.Database

    On Error GoTo Fail

    If Len(Dir$(srcPath)) = 0 Then
        Debug.Print "Source file not found: " & srcPath
        Exit Function
    End If

    ' Lock file exists while anyone is connected, so a copy now could be inconsistent
    If LCase$(Right$(srcPath, 6)) = ".accdb" Then
        lockFile = Left$(srcPath, Len(srcPath) - 6) & ".laccdb"
    Else
        lockFile = Left$(srcPath, Len(srcPath) - 4) & ".ldb"
    End If
    If Len(Dir$(lockFile)) > 0 Then
        Debug.Print "Database is in use. Backup skipped: " & lockFile
        Exit Function
    End If

    fileName = Mid$(srcPath, InStrRev(srcPath, "\") + 1)
    ext = Mid$(fileName, InStrRev(fileName, "."))
    baseName = Left$(fileName, Len(fileName) - Len(ext))
    dest = backupFolder & "\" & baseName & "_" & Format$(Now, "yyyymmdd_hhnnss") & ext

    FileCopy srcPath, dest

    ' Verify: sizes match and the copy actually opens read-only
    If FileLen(dest) <> FileLen(srcPath) Then Err.Raise vbObjectError + 1, , "Size mismatch"
    Set testDb = DBEngine.OpenDatabase(dest, False, True)
    testDb.Close

    Debug.Print "Backup verified: " & dest
    BackupBackend = True
    Exit Function

Fail:
    Debug.Print "Backup failed: " & Err.Description
    BackupBackend = False
End Function

' Usage:
'   BackupBackend "\\server\share\Orders_Data.accdb", "\\server\backups\access"

Knowing Who Changed What

Specific Problems We Fix

• "Unrecognized database format" and the file will not open: what the error means, what to do before anything rewrites the file, and how recovery works.
• Compact and Repair fails, hangs, or made things worse: why it rebuilds rather than patches, and what to do instead.
• The database keeps corrupting over LAN, Wi-Fi or VPN: the causes behind repeated corruption, and the fixes that end it.
• The database opens but is painfully slow: tuning, indexing and splitting, which is a different problem from corruption.

What Access Database Repair Costs