Access 'ODBC--Call Failed': Find the Real Error and Fix It

Step 1: Read the Real Error

Public Function OdbcErrorDetail() As String
    Dim e As DAO.Error, s As String
    For Each e In DBEngine.Errors
        s = s & e.Number & " - " & e.Description & " [" & e.Source & "]" & vbCrLf
    Next e
    OdbcErrorDetail = s
End Function

' In an error handler:
Fail:
    If Err.Number = 3146 Then            ' 3146 = ODBC--call failed
        MsgBox OdbcErrorDetail(), vbExclamation, "Database error"
    Else
        MsgBox Err.Number & ": " & Err.Description
    End If

Common Causes and Fixes

Driver and Connection Strings

DSN-less connection string (Windows authentication):
ODBC;DRIVER={ODBC Driver 18 for SQL Server};SERVER=sql01.company.local;
DATABASE=Operations;Trusted_Connection=Yes;Encrypt=Yes;

With SQL authentication (avoid storing passwords in linked tables where possible):
ODBC;DRIVER={ODBC Driver 18 for SQL Server};SERVER=sql01;DATABASE=Operations;
UID=app_user;PWD=...;Encrypt=Yes;

Timeouts and Slow Queries

• Queries using Access functions (IIf, Nz, Format, custom VBA functions) in WHERE clauses may force Access to pull whole tables locally.

• Joining a local Access table to a SQL Server table also pulls data across the network.

• Move heavy aggregation into SQL Server views and link them, or use pass-through queries that run entirely on the server.

• Check server indexes on the columns used in joins and filters.

• Set ODBC Timeout per query (property sheet) only when a slow query is genuinely expected.

Errors When Saving Records

• Tables need a primary key in SQL Server to be updatable from Access; without one, links are read-only or rows show #Deleted.

• Add a rowversion column to frequently edited tables; Access uses it to detect changes efficiently and reduce write conflicts.

• Bit (Yes/No) columns should not allow NULL; set a default of 0, otherwise Access can raise write conflicts.

• Triggers that fail produce ODBC errors on save; the trigger's error message appears in DBEngine.Errors.

A Diagnostic Order That Saves Time

• Read DBEngine.Errors. The answer is there most of the time.

• Can the same user connect from the same PC with SQL Server Management Studio or a test DSN?

• Did anything change: driver update, server certificate, password policy, schema change?

• Is it one table or query, or every connection? One object points to schema or query issues; everything points to connection issues.

• Is it intermittent and worse remotely? Look at network and timeouts.