1

I am using Access 2013, with forms. There are inked tables from an Azure SQL Server 12.0 database. The tables are linked with an ODBC Data Source using the "SQL Server Native Client 11.0" driver. I saved the "SQL Server Authentication" password when importing the linked tables. There are 34 linked tables.

When I open the database, everything is OK and the forms return with data. Then, after a few minutes I get one of the following errors:

TCP Provider: An existing connection was forcibly closed by the remote host.

Or

ODBC--connection to 'Data Source' failed.

And after the database connection error, nothing works anymore.

Any help will be greatly appreciated.

I've tried google, Bing, the new Bing AI chat, ChatGPT. I have tried reimporting the Azure SQL database tables and saving the SQL Server Authentication password.

EDIT: I have installed the "ODBC Driver 18 for SQL Server" and restarted the machine. I have then recreated the Data Source Name (DSN) using the new driver. I have also relinked the tables from the database in Access 2013.

I continue to get the same errors but with the new driver name in the error window instead.

Error 1:

connection forcibly closed

Error 2:

connection broken

Error 3:

enter image description here

It maybe some sort of networking problem?

Christopher Page
  • 19
  • 6
  • [Please do not upload images of code/data/errors when asking a question.](//meta.stackoverflow.com/q/285551) – Thom A Jun 05 '23 at 15:44
  • 1
    Linked ODBC tables in Access are very sensitive to network interruptions (even if very short), these errors sound exactly like this. If you can't get a rock-solid network connection to the server, you may have to rethink your system. E.g. no bound forms, load/save all data via code. – Andre Jun 06 '23 at 13:32
  • @Andre: Yes it looks like a network problem. Thanks for the replies. – Christopher Page Jun 13 '23 at 15:38

1 Answers1

2

SQL Server Native Client (SNAC) is a legacy and deprecated provider and has been removed from SQL Server 2022 and tools like SSMS, SNAC is not recommended to connect to Azure SQL read more here. Please install the latest ODBC Driver for SQL, restart the computer, and create the ODBC DSN using this new driver. Here is how to do it.

Alberto Morillo
  • 13,893
  • 2
  • 24
  • 30