Web Sablime® create/fcreate errors with
Netscape 4.7x and Netscape 6.0

Updated Tuesday,30-Sep-03 14:28:11 EDT

Description:

On Web Sablime®, some web browsers have problems with the create/fcreate commands due to a JavaScript function which manipulates the "module" field. On Internet Explorer, the "module" field is correctly updated for the selected system and subsystem. On Netscape 4.7x, the module field remains blank even when valid modules exist for the selected system/subsystem combination. On Netscape 6.0, the create/fcreate screens fail to load due to a DLL file error. This occurs when there are a large number of entries in the 'subCASmod' cascading relation. The JavaScript function created to map these Systems and Subsystems to the appropriate Module apparently causes problems for Netscape 4.7x and Netscape 6.0 web browsers because of its size.

NOTE: This problem is different from previous cascading problems which were fixed for Web Sablime® 2.0 update 2

Affected systems:

Web Sablime® 2.0 update 2 and earlier versions of Web Sablime®

Fixed in Sablime® release:

This problem has not been resolved in any official version of Web Sablime® yet. However, there is a patch available to resolve this issue.

How to test for presence of this issue:

This problem may exist if there are a very large number of entries in the 'subCASmod' cascading relation.
This problem exists if:

1) the "module" field on the create/fcreate screens work correctly with Internet Explorer

AND one or both of the following are also true:

1) with Netscape 4.7x, the "module" field on the create/fcreate screens remains blank even when valid modules exist for the selected system and subsystem
2) with Netscape 6.0, the create/fcreate screens cause a DLL error and cause the browser to terminate

Workarounds:

Use only Internet Explorer or versions of Netscape which do not have this problem.

OR

Download the updated commands.pl Web Sablime® patch.

To download the file directly to your disk, hold down the SHIFT KEY and click on the file.

NOTE: Modify the first line in the commands.pl to point to the proper Perl location.