User`s guide

User’s Guide 17
first. If the check fails, the file cannot be opened and an error
message will appear in the instrument activity log. Checksum
verification, when enabled, is enterprise-wide. The checksum
feature is enabled from the Enterprise Options dialog in the
Main menu, and is labeled Extended Security. GLP and
Extended Security
Turn on Extended Security
In order to adhere to good laboratory practices, the software
does not let you over-write a data file. If you try to over-write
an existing data file name, the system will either give you an
error message, or trigger a failure action if encountered
during a Sequence operation.
If, for some reason, you wish to ignore GLP and have access
to over-writing of data files, your files must be located in a
directory whose path contains the term "public". For example,
if your data files are saved in a folder entitled "\Public\Data",
the software files saved in this folder can be overwritten.
Extended Security
To turn ON Extended Security,
1. From the Main Menu, click Tools followed by
Options... and then select the General tab.
2. Click Extended Security if the box is not selected
already.
This selection is ON by default. When this option is selected,
causes a checksum to be calculated whenever a data file is
closed. When the file is subsequently opened, its checksum is
verified first. If the check fails (the calculated checksum for
the file does not match the one previously calculated for the
file) the file cannot be opened, and an error is posted in the
instrument activity log. Checksum verification is enterprise-
wide.
View the Method Audit Trail
Each Method file can have an Audit Trail enabled. When this
is enabled, changes to the method will be logged in the file