The Problem (Q-score 6, ranked #59th of 67 in the Access VBA archive)
The scenario as originally posted in 2011
I’m building a desktop app that needs to communicate with a MS Access database. Now, unless I want to register the DSN for the database on every computer that’s going to use the desktop app, I need a way to connect to the database in a DSN-less fashion.
I’ve searched alot and found some useful links on how to create connection strings and based on that I tried modifying my program based on that but without success.
The code below fails. If i switch the string in the getConnection to “jdbc:odbc:sampleDB” it works, but that’s using DSN and not what I want to achieve.
How do I write and use a connection string in java to make a DSN-less connection to a MS Access database?
private Connection setupConnection() throws ClassNotFoundException,
SQLException {
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection con = DriverManager.getConnection("Driver={Microsoft Access Driver (*.mdb)} &_ Dbq=c:\as\sampleDB.mdb");
return con;
}
Addition: I’d also like to point out that if anyone has an idea of a way to achieve what I asked for WITH a DSN-connection I’ll gladly listen to it!
Why community consensus is tight on this one
Across 67 Access VBA entries in the archive, the accepted answer here holds niche answer (below median) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — niche answer (below median) (+5)
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.
JDBC connection string shouls start with jdbc: like:
jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=c:\Nwind.mdb
so try with:
Connection con = DriverManager.getConnection("jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};Dbq=c:\as\sampleDB.mdb");
If you configure DSN then you can connect to it using simplier connect string: jdbc:odbc:[alias], example:
jdbc:odbc:northwind
When to Use It — vintage (14+ years old, pre-2013)
Ranked #59th in its category — specialized fit
This pattern sits in the 84% 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 2011 and 2026
The answer is 15 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.