The Problem (Q-score 10, ranked #26th of 67 in the Access VBA archive)
The scenario as originally posted in 2010
I have a program which needs to upgrade any Access (Jet) database it opens to JET Version4.x if it isn’t already that version. (This enables use of SQL-92 syntax features)
Upgrading is (relatively) easy. A call to the JRO.JetEngine object’s CompactDatabase method (as described here) should do the trick, but before I do this I need to determine whether an upgrade is required. How do I determine the Jet OLEDB:Engine Type of an existing database? Can this be determined from an open OleDBConnection?
Note:
- I’m talking about database versions, not Jet library versions.
- C# or .Net solution greatly appreciated.
- This is an application which uses the Jet engine, NOT an Access application.
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) (+4)
3-line Access VBA pattern (copy-ready)
You’ll have to set a reference to ADO and then you can get the property.
From inside of Access
Dim cnn As ADODB.Connection
Set cnn = CurrentProject.Connection
From outside of Access
Dim cnn As New ADODB.Connection
cnn.Open Provider=Microsoft.Jet.OLEDB.4.0;Data Source=Contact.mdb
And finally
Debug.Print cnn.Properties("Jet OLEDB:Engine Type").Value
This .Value will return 1 to 5. If it is 5, it is already in Jet4x, otherwise it is an earlier version.
Here’s another example of the upgrade technique you’re looking at as well: Convert MDB database to another format (JET, access version)
When to Use It — vintage (14+ years old, pre-2013)
Ranked #26th in its category — specialized fit
This pattern sits in the 87% 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 2010 and 2026
The answer is 16 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.