A family of Microsoft relational database management systems designed for ease of use.
If the Add Tables option was available once and is now missing for both existing and new ODBC sources in Access, check the ODBC data source configuration first.
- Verify the correct ODBC driver is installed.
- Access requires the appropriate driver for the external database.
- If the driver is missing or incorrect, table discovery can fail.
- Recreate or review the DSN in ODBC Data Source Administrator.
- Open Control Panel > Administrative Tools > Data Sources (ODBC).
- Check whether the DSN was created as User DSN, System DSN, or File DSN.
- Select the DSN and review its settings.
- Confirm the server name, database name, and authentication details are still correct.
- Make sure the DSN points directly to the target database.
- A data source includes connection information such as server location, database name, logon ID, password, and driver options.
- If the database setting is wrong, Access may connect but not show the expected tables.
- If using Azure SQL with Access, avoid older or incompatible SQL Server ODBC behavior.
- One documented cause of missing tables is Access attempting to reference
master.sysdatabases, which Azure SQL Database does not support. - In that case, use a modern SQL Server ODBC driver and configure the DSN to connect directly to the target database.
- A reported workaround is to try ODBC Driver 17 if ODBC Driver 18 is not working correctly in Access.
- One documented cause of missing tables is Access attempting to reference
- Re-add the data source if needed.
- In Data Sources (ODBC), choose the DSN type, select Add, choose the correct driver, and complete the connection information.
- This requires local administrator membership to add or configure an ODBC data source.
- If the issue started after it worked once, remove stale or unused DSNs.
- In odbcad32, review both User DSN and System DSN.
- Remove old entries that are no longer used, then restart Access and test again.
If the environment is Azure SQL, the most likely fix is to create a DSN that is pinned to the target database and then link tables again from Access.
References:
- Administer ODBC data sources
- Recently, ODBC connections to our database in Azure no longer show all available tables. - Microsoft Q&A
- Access Database Migration to Azure SQL DB fails - Microsoft Q&A
- Cannot establish ODBC 18 Connection via Interactive authentication - Microsoft Q&A
- microsoftt access problem - Microsoft Q&A