Fix Access Migration Wizard Not Finding Tables in SQL Server Express
Question details
The user needs to migrate Access tables to SQL Server Express when the migration wizard cannot display the tables or reports a connection error.

- Product
- Microsoft Access, SQL Server Express, and SQL Server Migration Assistant for Access
- Device & OS
- not provided
- Scenario
- Migrating an Access database to a SQL Server Express instance while retaining an Access front end.
- Observed behavior
- The wizard does not display the expected tables or returns a network-related connection error.
Locate the Access database file and identify the SQL Server Express computer and instance name. Confirm that you have permission to open the Access tables and connect to the SQL Server instance.
Check the Access source and SQL Server Express connection
Use these checks when tables are missing from the migration tool or the connection to SQL Server fails.
Open the database in Microsoft Access and check the Navigation Pane for the tables you want to migrate. If a table is linked to another source, open it to confirm that its source is available.
In SQL Server Migration Assistant (SSMA) for Access, use Add Databases to select the Access file, then expand it in Access Metadata Explorer to check its tables.
Open SQL Server Configuration Manager and select SQL Server Services. Find the running SQL Server instance and note its name; a typical Express instance is SQLEXPRESS.
In the migration tool's SQL Server connection dialog, enter the computer and instance name, such as ComputerName\SQLEXPRESS. For a local connection, select Windows Authentication if your Windows account has SQL Server access.
In SQL Server Configuration Manager, start the SQL Server service if it is stopped. Under SQL Server Network Configuration, check the instance's protocols; enable TCP/IP if needed for a network connection and restart the SQL Server service after changing protocol settings.

Repair or reinstall the migration components
Use this approach if the source and connection settings are correct but migration still fails.
Check Access front-end references after migration
Use this after migration if linked table names differ from the names expected by the Access front end.
Work with Office files in WPS Office
WPS Office is a free, lightweight alternative for everyday documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format support make it easier to move compatible files into a different office suite. It does not replace Access or perform Access-to-SQL Server migrations.

Frequently Asked Questions
What server name should I enter for SQL Server Express?
In the migration tool's SQL Server connection dialog, enter the computer name and named instance, such as ComputerName\SQLEXPRESS. Check the actual instance name under SQL Server Services in SQL Server Configuration Manager.
Why are my Access tables missing from SSMA?
Confirm that you added the correct database through Add Databases, then expand it in Access Metadata Explorer. Open the file in Access to verify that the tables are present and accessible, including any linked tables.
Can I use Windows Authentication for a local connection?
Yes, if your Windows account has permission to connect to the SQL Server instance. Select Windows Authentication in the migration tool's connection dialog.
Why do my linked tables have a dbo_ prefix?
Access linked table names can include a dbo_ prefix after linking to SQL Server. Compare the names in the Navigation Pane with your front-end references, and use Linked Table Manager or update affected references as needed.
Can WPS Office migrate an Access database to SQL Server?
No. Use an Access migration tool such as SSMA for Access for that task. WPS Spreadsheets can work with compatible spreadsheet files, such as XLSX data exported from Access.




