英文:
Why is my Access 2013 ODBC SQL Server Data Source failing after a few minutes?
问题
我正在使用 Access 2013，使用表单功能。
这些表格是来自 Azure SQL Server 12.0 数据库的链接表格。
这些表格通过使用 "SQL Server Native Client 11.0" 驱动程序连接到 ODBC 数据源。
我在导入链接表格时保存了 "SQL Server 身份验证" 密码。
总共有 34 个链接表格。
当我打开数据库时，一切正常，表单会返回数据。
然后，几分钟后，我会收到以下错误之一：
或
在数据库连接错误之后，再也无法正常工作。
任何帮助将不胜感激。
我尝试过谷歌、必应、新的必应人工智能聊天、ChatGPT。
我尝试过重新导入 Azure SQL 数据库表格并保存 SQL Server 身份验证密码。
编辑：
我安装了 "ODBC Driver 18 for SQL Server" 并重新启动了机器。然后我使用新的驱动程序重新创建了数据源名称 (DSN)。我还在 Access 2013 中重新链接了来自数据库的表格。
但我仍然收到相同的错误，只是错误窗口中显示了新的驱动程序名称。
错误 1：
错误 2：
错误 3：
可能是某种网络问题？
英文:
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:
Error 2:
Error 3:
It maybe some sort of networking problem?
答案1
得分: 2
SQL Server Native Client (SNAC) 是一个已过时和弃用的提供程序，已从 SQL Server 2022 和诸如 SSMS 这样的工具中移除，不建议使用 SNAC 连接到 Azure SQL，请在此处阅读更多信息。请安装最新的 ODBC Driver for SQL，重新启动计算机，并使用这个新驱动程序创建 ODBC DSN。以下是如何操作的步骤。
英文:
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.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论