'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Access Linked Table Errors Caused by Database Name Case
Question details
The user needs to fix an issue where Microsoft Access linked tables fail to connect to a Snowflake database via ODBC because of capitalization differences in database and object names.
- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Migrating or changing an existing ODBC connection to Snowflake, which causes linked tables to break if object names are not properly cased.
- Observed behavior
- Access returns a 'table does not exist' error because it runs catalog queries that fail when the casing does not strictly match Snowflake's case-sensitive requirements.
Verify the exact case-sensitive spelling of your Snowflake database, schema, and table names before attempting to repair the linked tables in Access.
Delete and Recreate Linked Tables Using Exact Source Casing
Because Access does not offer a setting to disable case-sensitive catalog searches for ODBC connections, you must recreate the links using the precise capitalization expected by Snowflake.
When Access performs a catalog search (like SHOW COLUMNS IN ACCOUNT) against case-sensitive target databases such as Snowflake, it requires a perfect case match. Since you cannot force Access to ignore casing, the most reliable method is to rebuild the links.
Log into your Snowflake environment and note the exact uppercase or lowercase formatting used for your target database, schema, and tables.
In Microsoft Access, locate the broken linked tables in the Navigation Pane. Right-click each one and select 'Delete', or use 'TableDef.Delete' in VBA to remove them programmatically.
Open the VBA Editor and use the 'DoCmd.TransferDatabase acLink' command to establish the new connection. Ensure that the 'Source' argument exactly matches the case required by Snowflake.
While the source table name must be case-perfect, you can set the 'Destination' argument (the linked-table name within Access) to whatever capitalization fits your internal naming convention.
Need a Fast, Lightweight Alternative to Microsoft Office?
If you are looking for a highly compatible and budget-friendly alternative to Microsoft Office for your daily document, spreadsheet, and presentation tasks, WPS Office is an excellent choice. It offers powerful features without the heavy system requirements.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install WPS Office: Run the setup file and follow the straightforward on-screen instructions to complete the installation.
- 3. Open Your Files: Launch WPS Office and instantly open your existing .docx, .xlsx, and .pptx files with perfect formatting preservation.
Frequently Asked Questions
Why does Microsoft Access say my Snowflake table does not exist?
When connecting via ODBC, Access runs catalog queries to find the tables. If the target database (like Snowflake) enforces case-sensitive object names, a mismatch in capitalization will cause Access to think the table is missing.
Can I disable case-sensitive catalog searches in Microsoft Access?
No, Access does not provide a native setting or configuration option to turn off case-sensitive catalog searches. The best workaround is to ensure the source names used in your connection string match the database precisely.
Do I have to change my table names inside Access?
Not necessarily. The strict case requirement only applies to the source table name defined in the ODBC connection. Once the table is successfully linked, you can rename the local table alias in the Access Navigation Pane to whatever you prefer.
