c:JAM cannot be started. Immediately after the splash screen a windows error message informs me that c:JAM application has detected a problem and has to be closed.

In some rare Windows XP configurations EvtSrc.dll does not initialize correctly. Please rename the file EvtSrc.dll in the c:JAM program folder and restart c:JAM. This workaround disables scripting functionality.

[c:JAM v1.5 - fixed]

I can't explore databases secured with Access 2000 Security Wizard anymore. Why do I get the c:JAM error message "DAO-Error 3112: Record(s) cannot be read; no read permission on 'Databases'."?

The Access 2000 Security Wizard restricts access to the 'Databases' container and system tables like AccessLayout, SummaryInfo, UserDefined, MSysACEs and MSysObjects in an undocumented way. Even members of the admins group are no longer permitted to read any account's access permissions to these objects beside that of their own.
This behaviour can be reproduced within MS-Access. The options to show hidden and system-objects have to be checked in order to do that.
c:JAM cancels 'read permission' requests of any user account, which is not even able to read the permissions of the 'Databases' container. This behaviour has been changed now, because it's no longer compatible with Access Security Wizard.
If you require this change, please download the patch cjam14fix2.zip, extract the archive and copy the extracted files into your c:JAM installation folder.

[c:JAM v1.4 - fixed]

A mouse right click on a displayed 'Unit' causes c:JAM to terminate immediatly upon a system error message ('invalid page in MFC42.DLL'). Is a patch for this problem available?

Yes, a patch to this localization problem exists. The 'Unit' context menu has been incorrectly declared in some c:JAM v1.4 US engl. distributions. Please download the patch cjam14fix1.zip, extract the archive and copy the extracted files into your c:JAM installation folder.

[c:JAM v1.4 - fixed]

c:JAM immediately terminates upon start reporting a runtime error. What does this message mean?

The v1.4 setup program doesn't correctly register the DAO 3.6 libraries after installing the files. So the above error may occur in environments where DAO 3.6 isn't preinstalled. To work around this problem, register the DAO 3.6 libraries manually. Call

<SystemDir>\Regsvr32.exe
<SharedFiles>\DAO\Dao360.dll

where <SystemDir> is typically "c:\windows\system" or "c:\winnt\system32" and <SharedFiles> is typically "c:\program files\common files\microsoft shared"

or execute the patch file regdao.exe provided on our web site.

Please also check whether ddao36.dll, dao360.dll and msjet40.dll are present on your system.

[c:JAM v1.4 - fixed]

What does the error message "Cannot create document" mean?

c:JAM v1.4 uses Internet Explorer 4 style toolbars. The error message "Cannot create document" indicates, that required system libraries are not installed.
Install Internet Explorer 4 (or higher) or run 40comupd.exe from our web site.

[c:JAM v1.4]

Why do I get a message that the system time has been manipulated and that the evaluation period has expired? Since I have never used the product, this is clearly wrong.

Initializing the evaluation period may fail in some NT and W2000 environments, so c:JAM cannot be startet. The program displays a misleading error message ("Systemtime manipulated") and returns. The problem might disappear some hours after the first installation.
To resolve the problem, please download and copy the file cjam135.exe (17 kb) into your c:JAM installation directory (e.g. c:\program files\jomdev webware\cjam). Execute the file and type 'y' when prompted whether to overwrite jmitxl32.dll.

This problem only affects unregistered versions of c:JAM v1.3.

[c:JAM 1.3 Unreg. Shareware - fixed in v1.4]

Why does the OLE Automation Function GetAccountsTree() sometimes return "Nothing"?

There is a known bug in the c:JAM v1.3 Open(cWorkgroupFile, cServiceAccount, cServicePassword) Function. The cServiceAccount and cServicePassword arguments are evaluated too late - after the document has been opened and the workgroup has been loaded. So if the required account / password information isn't stored in the c:JAM document, Open() opens the document, but can't load the workgroup. The next call to GetAccountsTree() returns Nothing, because c:JAM has not been able to analyze the account-information.

To work around this problem, call Open() twice: the first call should only set account information, the second call actually opens and loads the workgroup. Here's a VBScript sample

Set WG = CreateObject("cJAM.Workgroup")
WG.Open(cWorkgroupFile, cServiceAccount, cServicePassword)
Set TREE = WG.GetAccountsTree("")
If TypeName(TREE) = "Nothing" Then
WG.Open(cWorkgroupFile, cServiceAccount, cServicePassword)
Set TREE = WG.GetAccountsTree("")
Endif

Or store account and password information in the c:JAM document file (encrypted). If this information can be retrieved from the file, account information is available at load time and everything runs like expected.

[c:JAM 1.3 Automation - fixed in v1.3b (1.3.0.3)]

If c:JAM runs as an Automation Server, some instances seem not to terminate.

Once c:JAM is started per OLE-Automation, the program should pass out no interactive messages and dialogs. If two conditions however apply simultaneously, it may occur that a dialog nevertheless pops up. If a c:JAM document file contains UNC pathnames (1) and one of these pathnames could not be found or access-entitlements are missing (2), c:JAM may try to initiate a network-connection. On this occasion it's possible that the system requests account and password information. If the server program is running in the context of a service without user interface, it's possible that the process waits indefinitely for user-input.

To work around this problem, use drive mappings instead of UNC pathnames to reference systemdatabase files in a c:JAM workgroup. In this case, c:JAM works correctly even in the case of missing access authorization: the process immediately terminates.

[c:JAM 1.3 Automation - fixed in v1.3b (1.3.0.3)]