"ODBC--call failed" error when you open a table that is linked to a SQL Database instance in Access
Consider the following scenario:
- A table has lots of records in a Microsoft Azure SQL Database instance.
- The table is added as a linked table in Microsoft Access.
- You try to open the linked table in Access.
ODBC--call failed: [Microsoft][SQL Server Native Client 11.0]TCP Provider: An existing connection was forcibly closed by the remote host (#10054) [Microsoft][SQL Server Native Client 11.0]Communication link failure (#10054)
Note This issue may also occur when you try to open the linked table from other applications that are connected to the SQL Database instance table by using Microsoft Open Database Connectivity (ODBC).
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around this issue, use one of the following methods:
- Click Last record as soon as the table is opened in order to display all records in the linked table in the Datasheet View of Access.
- Do not select all records in the linked table to be displayed. Instead, select only a limited number of records.
For more information about Access 2010 and SQL Database (referred to as SQL Azure on this blog), go to the following Microsoft Office blog:
209126 Information about query performance in an Access database
Article ID: 2730109 - Last Review: 10/01/2015 03:01:00 - Revision: 9.0
Microsoft Access 2010, Microsoft Azure SQL Database, Access 2016, Microsoft Office Access 2007, Microsoft Access 2013
- kbsurveynew kbtshoot kbprb KB2730109