The Problem (Q-score 7, ranked #17th of 67 in the Access VBA archive)
The scenario as originally posted in 2012
I’m using DSN-less connections to my SQL Server in an Access database. However, whenever I try to write a “Pass-Through” query and run it, a dialog box pops up asking for the DSN.
Why community consensus is tight on this one
Across 67 Access VBA entries in the archive, the accepted answer here holds strong answer (top 25 %%) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — strong answer (top 25 %%) (+14)
Advisory answer — community consensus with reference links
Note: the verified answer below is a reference / advisory response rather than a copy-ready snippet.
In SQL view, choose properties after you have selected passthrough query and insert an ODBC connect string. For example:
ODBC;DRIVER=SQL Server;SERVER=ServerInstance;Trusted_Connection=Yes;DATABASE=Test
See also: http://www.connectionstrings.com/sql-server-2008
When to Use It — vintage (14+ years old, pre-2013)
Ranked #17th in its category — specialized fit
This pattern sits in the 55% 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 2012 and 2026
The answer is 14 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.