c:JAM v1.3 supports Microsoft Jet versions 2.0, 2.5, 3.0 and 3.5, even simultaneously and in the same workgroup. c:JAM 1.4 adds support for Jet 4.x

Jet 2.0	Access 2.0	Office 4.x	VB 3.0 plus VBCL
Jet 2.5	Access 2.0 SP	Office 4.x	VB 3.0 plus VBCL
Jet 3.0	Access 7.0	Office 95	Visual Basic 4.0	Visual C++ 4.x
Jet 3.5	Access 8.0	Office 97	Visual Basic 5.0	Visual C++ 5.0
Jet 4.0	Access 2000/XP	Office 2000/XP	Visual Basic 6.0	Visual C++ 6.0
Jet 4.0	Access 2003	Office 2003	Visual Basic 7.0/8.0	Visual C++ 7.0/8.0

Table: supported Jet Versions and Jet based Tools & Applications

c:JAM v1.3 uses DAO 3.0 to access Jet 3.0 database files. MSRD2X32.DLL is used to extend DAO 3.0 to manipulate Jet 2.x format database files. c:JAM v1.4 and v1.5 use DAO 3.6 to access Jet 4.0 database files. MSRD3X40.DLL and MSRD2X40.DLL are used to extend DAO 3.6 to manipulate Jet 3.x and 2.x format database files.

c:JAM cannot address Access 1.files. c:JAM 1.4 currently doesn't support 16bit Access 2.0 (Jet 2.0). This is due to an error in the available Jet 4.0 DLL's (probably MSRD2X40.DLL).

There is no format change in Jet 3.5 database files; thus, it is possible to access a database that was created with Jet 3.5 through DAO 3.0. Note: Microsoft Access 97 does require a conversion process, primarily due to a new method of storing Visual Basic for Applications, but not due to a Jet file format change.

Microsoft Access 2.0 and 7.0 store user preferences in the table AccessPreferences in the current workgroup information file. Microsoft Access 8.0 stores preferences in the windows registry under  HKEY_CURRENT_USER/ software/ microsoft/ office/ 8.0/ access/ settings. c:JAM's automatic generation of user defined   preferences for every new user account doesn't work with Jet 3.5 workgroup information files any longer, cause the table AccessPreferences no longer exists. c:JAM does not modify HKEY_USERS registry keys on all machines having access to the workgroup information file.

c:JAM v1.2 and v1.3 were build using Microsoft Visual C++ 4.1, MFC 4.0 and DAO SDK 3.0. c:JAM v1.4 and v1.5 are build with Microsoft Visual C++ 6.0, MFC 4.2 and DAO SDK 3.6.

We try to supply the newest technologies with our products. Jan 97, when c:JAM 1.2 was published, DAO 3.0 has been the most suitable way to access Microsoft Jet files. Visual C++ 4.2 had many severe bugs at that time. And it was shipped with an incompatible version of the DAO SDK, which causes run time errors during execution (see Knowledge Base article Q158500). When this problem has been solved at last, c:JAM 1.2 had been tested thorougly and prepared for release.

Oct 98 when c:JAM v1.3 was released, we dicided not to use up disk resources of our customers for CRT 4.2, MFC 4.2 and Jet 3.5 / DAO 3.5. c:JAM 1.3 has a reliable runtime behavior and works fine even with the new Jet 3.5 files. So there was no reason to switch to DAO 3.5.

See Online Documentation for a list of files, that ship with your c:JAM version .