The Problem (Q-score 4, ranked #25th of 67 in the Access VBA archive)
The scenario as originally posted in 2009
I’m looking after a database while its author is on holiday. The server it’s running on has no linked table manager, and the db is giving me an error – “ODBC –connnection to ‘XYZ’ failed.” when I try to Domd.OpenQuery a query that’s depending on a linked table.
I get the same message when I try to open said linked table. How do I find out where it’s pointing to?
Why community consensus is tight on this one
Across 67 Access VBA entries in the archive, the accepted answer here holds solid answer (above median) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — solid answer (above median) (+10)
Verbal answer — walkthrough without a code block
Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Access VBA entries ranked in the top 10 of the same archive.
Open the table in design mode, accept the warning with “Yes”, look into the “Properties” window of the table (not the one of the column — in Access 2007, the table properties window is docked on the right-hand side of the window; in earlier versions there’s a button in the tool bar, if I remember correctly). The “Description” field contains the ODBC string for the table.
When to Use It — vintage (14+ years old, pre-2013)
Ranked #25th in its category — specialized fit
This pattern sits in the 68% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Access VBA archive for a higher-consensus alternative.
What changed between 2009 and 2026
The answer is 17 years old. The Access VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.