Fix Microsoft Access SQL Server Linked Table Errors 772 and 18
Question details
Restore access to SQL Server linked tables in Microsoft Access after a move from TLS 1.1 to TLS 1.2.

- Product
- Microsoft Access and SQL Server
- Device & OS
- not provided
- Scenario
- An Access database uses ODBC-linked tables from a SQL Server environment that has changed to TLS 1.2.
- Observed behavior
- Linked tables may fail to open or refresh, with errors 772 and 18.
Confirm the SQL Server name, instance, database, authentication method, and DSN used by the affected tables. In Access, check File > Account > About Access for the application bitness so you can verify that a matching ODBC driver is installed.
Refresh or relink the SQL Server tables in Access
Use Linked Table Manager to refresh existing links or recreate their connection details after the server change.
In Access, open the affected database and select External Data > Linked Table Manager.
Select the affected SQL Server linked tables and choose Refresh. Try opening a table after the refresh completes.
In Linked Table Manager, select the affected tables and choose the relink option. In versions that show it, enable Always Prompt for New Location, then proceed to select or recreate the ODBC connection.
In the ODBC connection or DSN setup dialog, check the server, instance, database, and authentication details. Complete the prompts and try opening the linked tables again.

Check the ODBC driver and TLS 1.2 support
Use this check if refreshing or relinking does not restore the connection.
Work with Office files in WPS Office
WPS Office is a free, lightweight alternative for everyday document, spreadsheet, and presentation work. Its familiar interface and Microsoft Office format compatibility make it easy to move existing files. It does not repair Access connections or replace Access linked-table functionality.

Frequently Asked Questions
Where is Linked Table Manager in Access?
Open the database and select External Data > Linked Table Manager. The available refresh and relink controls can vary by Access version.
Do I need a 32-bit or 64-bit ODBC driver?
Use a driver that matches Access bitness. Check File > Account > About Access, then inspect the corresponding ODBC Data Source Administrator.
Why does the connection still fail after updating the ODBC driver?
The DSN or linked tables may still use outdated connection details, or the server, network, authentication, or TLS settings may need attention. Test the DSN in ODBC Data Source Administrator and verify the server and database names.
Can a file DSN help when relinking Access tables?
A file DSN can simplify connection setup and deployment. When relinking through Linked Table Manager, select or create the file DSN; Access may convert the resulting link to a DSN-less connection.




