"ODBC–call failed" error when you open a table that is linked to a SQL Database instance in Access 2010

Consider the following scenario:
  • A table has lots of records in a Windows Azure SQL Database instance.
  • The table is added as a linked table in Microsoft Access 2010.
  • You try to open the linked table in Access 2010.

In this scenario, you receive an error message that resembles the following:

ODBC–call failed: MicrosoftSQL Server Native Client 11.0TCP Provider: An existing connection was forcibly closed by the remote host (#10054) MicrosoftSQL Server Native Client 11.0Communication 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 2010.
  • 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:For more information about query performance in an Access database, click the following article number to view the article in the Microsoft Knowledge Base:
209126

(http://support.microsoft.com/kb/209126/
)

Information about query performance in an Access database

Article ID: 2730109 – Last Review: July 20, 2012 – Revision: 6.0


Applies to
  • Microsoft Access 2010
  • Microsoft SQL Azure Database
kbsurveynew kbtshoot kbprb KB2730109

More:
"ODBC–call failed" error when you open a table that is linked to a SQL Database instance in Access 2010

Comments are closed.

Recent Comments

    Archives

    Categories