With each new version of Microsoft Jet, enhancements in functionality and changes to the structure of the database file cause problems with backward compatibility. Wherever possible, efforts have been made to ensure an easy migration path between versions. However, incompatibilities do exist. The following table illustrates how database files and objects can be used with different versions of Microsoft Jet.
|
Microsoft Jet version |
|||||||
|
1.0 |
1.1 |
2.0 |
2.5 |
3.0 |
3.5 |
||
|
.Mdb (Microsoft Access) version |
1.0 |
Y |
Y |
Y |
Y |
Y |
Y |
|
1.1 |
N |
Y |
Y |
Y |
Y |
Y |
|
|
2.0 |
N |
N |
Y |
Y |
Y |
Y |
|
|
7.0 |
N |
N |
N |
N |
Y |
Y |
|
|
8.0 |
N |
N |
N |
N |
N |
Y |
|
A “Y” indicates that the database can be used without conversion; “N” indicates that the database can’t be used or converted.
By using DAO, you can open databases created with the version of Microsoft Jet that is running the DAO code, and those created with any previous version of Microsoft Jet. For example, if you’re running DAO code by using Microsoft Jet 3.0, you can open version 1.0, 1.1, 2.0, 2.5, and 3.0 databases, but not 3.5 databases.