Is c:JAM fully compatible with Access 2000, XP and 2003?

A: Yes. However, you should note that Access 2000 and above no longer stores modules in the Microsoft Jet Modules Container object and that the Jet database engine will ignore any permissions set on modules.
To properly secure all modules in Access 2000, XP or 2003 databases, you should lock the database's VBA project. VBA projects are not managed by c:JAM.

[c:JAM 1.4, c:JAM 1.5]

I'm a registered user but I didn't completly understand what I should do with my license file.

Please copy the license file cjam.lic into the installation directory of your shareware copy. The default installation directory is c:\program files\jomdev webware\cjam. This should turn off any limitations of your installation. But note: c:JAM v1.3 introduced personalized license files. The license file's name and company settings must match exactly name and company, entered during program setup.

Open the application's About Dialog to look for your installation's user name and company settings. The information is stored in the Name and Company variables of registry key "HKLM\Software\Jomdev Webware\c:JAM - Central Jet Accounts Manager\1.3.0.2". Open the license file with a text editor to view <name>@<company> of the license file. If there is a mismatch, you should reinstall the software using the registered name and company settings. It's also possible to change the registry values either direct or by double clicking on the reg file, delivered with the license file. Note c:JAM v1.4 lets you change name and company settings through the About Dialog.

[c:JAM all versions]

I'm missing MS Jet Engine 4.0. Where can I get the software?

If a Jet 4.0 component is missing, install the component from one of the software packages, listed in online help. Provided you don't have any of these packages, download the software from microsoft.com. See

msdn2.microsoft.com/en-us/data/aa937730
msdn2.microsoft.com/en-us/library/ms810805
support.microsoft.com/?kbid=829558
support.microsoft.com/kb/239114

Please notice, MDAC version 2.6 and later do not contain Jet or Desktop ODBC drivers any longer. You have to install the latest Jet 4.0 Service Pack on top of the Microsoft Data Access Components (MDAC). See

support.microsoft.com/kb/271908
The MDAC 2.5 Stack
MDAC 2.5

[c:JAM 1.4, c:JAM 1.5]

Creating an user account, that already exists, doesn't yield an error message. Isn't it a bug?

This behavior is by design. In an environment, where operations might affect a large count of units, different units should be considered a normal case. If the account has been created in every unit, where it doesn't already exists, the user should not be alerted. The action protocol shows what c:JAM has really done and what couldn't be done. Only if the account does not exist in every unit, after the operation has finished, an error message must be shown.

In some cases c:JAM creates accounts implicitly. If e.g. an user should become a member of some group in every unit, in some of them he - the user account - might have to be created first. JAM doesn't display an error message, if a membership couldn't be established in some unit. It tries to solve the problem by its own. And it lists every action in its action protocol.

[c:JAM all versions]

I downloaded c:JAM 1.3 some days ago and I receive an "unable to automatically register DAO3032.DLL" error message during the installation process. How can I install the program?

c:JAM v1.2 and v1.3 require MS Jet Engine 3.0. To minimize download time of our customers, the Jet Engine has not been included into the v1.3 package again. Please copy the missing Jet 3.0 files MSJT3032.DLL, MSJINT32.DLL, MSRD2X32.DLL, MSJTER32.DLL, MSVCRT20.DLL, VBAR2232.DLL and VBAJET32.DLL into your windows system folder and repeat the installation to complete component registration. More information - e.g. tips where to get the files - you'll find in the c:JAM online documentation. If you can't get the files, please ask us to send them to you by email (about 1.5 MB).

[c:JAM 1.3 Express Package - Installation]

I've got the message "File MSJINT32.DLL not found. MS Jet 3.0 Engine may not be installed. See Online Help for how to install". What should I do?

MS Jet Engine 3.0 is missing. See the topic above.

If a Jet 3.0 component is missing, install the component from one of these software packages: Microsoft Office 95, Microsoft Office 7.0, Microsoft Access 7.0, Visual Basic 4.0 32-bit, Visual C++ 4.x, c:JAM - Central Jet Accounts Manager v1.2, or download DAOREDIS.EXE, a self-extracting file, from the Microsoft Software Library (MSL) or use Fast FTP Search (http://ftpsearch.ntu.no) to search for "daoredis" files (11/96, 2,2MB).

Tip: Use the -d option when running DAOREDIS.EXE to decompress the file and recreate the proper directory structure.

After the DLLs have been copied into the windows system folder, you have to relaunch c:JAM Setup. This is necessary to build the required configuration settings.

[c:JAM 1.3 Express Package - Installation]

What does the error message "DAO-Error 3041:Can't open a database created with a previous version of your application" mean?

This error message means that MSRD2X32.DLL is not installed correctly and that c:JAM can't read Access 2.0 system databases. Please deinstall and reinstall c:JAM again to verify that the DAO libraries are installed correctly. If the error still occurs, please check (1) whether a file <WinSysDir>\ MSRD2X32.DLL (>= 1/5/96, 245,520 byte) exists and (b) whether the registry variable win32, key HKLM\ software\Microsoft\Jet\3.0\Engines\Jet2.x refers on this file.

[c:JAM 1.3 Express Package - Installation]