Slow Microsoft Access Database? We Find the Bottleneck and Fix It

Access specialists since 2011 (15+ years). Last updated October 22, 2026. Applies to Access 2016, 2019, 2021, 2024 and Microsoft 365.

Why Access Gets Slow: Symptoms, Causes and Fixes

What Slowness Costs Your Business

10 Fixes You Can Try Yourself Before Hiring Anyone

• Back up the file, then run Compact and Repair (Database Tools > Compact and Repair Database). Do this on a copy if the file is large.

• Split the database if it is a single file: Database Tools > Access Database. Put the back end on the server and a copy of the front end on every user's local drive.

• Link to the back end with a UNC path (\\server\share\data.accdb), not a mapped drive letter, so every user resolves the same path reliably.

• Add indexes to every field you join on, filter by, or sort by (primary and foreign keys first). Do not index every field; extra indexes slow down writes.

• Turn off Name AutoCorrect (File > Options > Current Database). It adds overhead on every design change.

• Set Subdatasheet Name to [None] on tables. Access otherwise checks for related records every time a table opens.

• Replace DLookup, DCount and DSum calls inside query criteria and form record sources with joins.

• Avoid leading wildcards such as Like "*smith" in criteria; they cannot use an index.

• Open forms with a filtered record source or a WhereCondition, instead of loading an entire table and filtering afterward.

• Place the front-end folder in a Trusted Location so Access does not run security checks every time it opens.

How to Measure Which Query Is Slow (VBA)

' Standard module: modPerfTest
' Times how long a saved query takes to return ALL its rows.
Public Function TimeQuery(ByVal queryName As String) As Double
    Dim rs As DAO.Recordset
    Dim startTime As Single
    Dim elapsed As Single

    startTime = Timer
    Set rs = CurrentDb.OpenRecordset(queryName, dbOpenSnapshot)
    If Not rs.EOF Then rs.MoveLast          ' forces Access to fetch every row
    elapsed = Timer - startTime

    Debug.Print queryName & ": " & rs.RecordCount & " rows in " & _
                Format(elapsed, "0.00") & " seconds"
    rs.Close
    Set rs = Nothing
    TimeQuery = elapsed
End Function

' Usage (Immediate Window, Ctrl+G):
'   ?TimeQuery("qryOpenOrders")

Index the Fields That Matter (Access SQL)

-- Access SQL (run from a query in SQL view)
-- Index the field used to JOIN to the parent table
CREATE INDEX idxOrders_CustomerID ON tblOrders (CustomerID);

-- Index fields you filter and sort on often
CREATE INDEX idxOrders_OrderDate ON tblOrders (OrderDate);

-- Composite index for a common filter + sort combination
CREATE INDEX idxOrders_Status_Date ON tblOrders (Status, OrderDate);

Keep a Persistent Back-End Connection (VBA)

' Standard module: modBackendConnection
' Keeps one connection to the back end open for the whole session.
' This avoids Access repeatedly creating and tearing down the lock file
' (.laccdb) on the network share every time a form opens.
Private mBackend As DAO.Database

Public Sub OpenBackendConnection(ByVal backendPath As String)
    On Error GoTo ErrHandler
    If mBackend Is Nothing Then
        Set mBackend = DBEngine.OpenDatabase(backendPath, False, True)
    End If
    Exit Sub
ErrHandler:
    Debug.Print "Could not open back end: " & Err.Description
End Sub

Public Sub CloseBackendConnection()
    If Not mBackend Is Nothing Then
        mBackend.Close
        Set mBackend = Nothing
    End If
End Sub

' Call OpenBackendConnection from your startup form's Load event or an AutoExec macro,
' and CloseBackendConnection when the application quits.

What's Included in Our Access Database Optimization Service

• Free performance review: we measure where the time goes before quoting anything

• Query analysis and rewriting, including flattening nested queries and removing slow domain functions

• Index strategy and table structure tuning

• Front-end and back-end splitting, with a deployment method so every user gets their own local front end

• Form and report tuning: filtered record sources, lighter controls, faster load times

• Multi-user configuration: record-locking mode, persistent connection, concurrent edit conflicts

• Network and VPN tuning for shared and remote environments

• Compact, repair and cleanup of bloat and abandoned objects

• SQL Server or Azure SQL migration of the tables when tuning alone is not enough

• Before-and-after timing report and handover documentation

When Optimizing Is Not the Answer

Optimize, Repair, or Migrate: Which One Do You Need?

What Fixing It Looks Like in Practice

How Much Does Access Database Optimization Cost?