Program Settings—GLOBALSETTINGS for CCLASMGR

Laboratory accreditation.

{Text}

If enabled, a scheme’s Complete status is reset when a result is deleted from a analyte, or a data value is changed and a status value other than Complete results the change.

Enabled | Disabled

The URL of the splash screen file, located in the folder defined by the %PictureDirectory% global setting, displayed when CCLAS starts up.

Example: %CCLASRootDirectory%Picture\CCLAS.BMP

The user-specific tables included in the off-line archive when the clsBDProfJob.ArchiveJob method is used to archive jobs. This is the original style of archiving that saves the job to a ZIP file that contains XML files of the archived data. Each of these settings contains a custom user table name that are not normally a part of the CCLAS database.

{DatabaseTableName}

The data source for the destination database.

For Oracle databases, this is the NET Service name set up on the computer. For SQL Server databases this is the name of the database prefixed by the server on which it resides (that is, Server;Database). The server prefix may not be required if a local database.

{DataSource}

Indicates whether an overwrite is forced if the job already exists in the destination database.

Enabled | Disabled

Enabled | Disabled

The folder where ident files are archived. If the folder is undefined, then the archiving process uses the value of the CCLAS Idents folder from the destination database (provided there is value).

{FolderName}

{EncryptedPassword}

The database provider for the destination database. Selected from:

• MSDAORA for Oracle
• MSDASQL for SQL Server.

{DatabaseProvider}

The tables to archive to the off-line archive when the asTables parameter is not specified.

This method is the new style of archiving where the tables for archiving are passed through as parameters to the method. Each of these settings contains a table name, and can include custom user tables that are not normally a part of the CCLAS database. Generally these settings contain the PROFJOB and the AUDITJOB tables, so if no items are in the array, the entire job and its audit trail is archived as a default.

Selected from:

• PROFJOB
• PROFJOBUSER
• PROFJOB_SCHEME
• PROFJOB_SCHEME_ANALYTE
• PROFJOB_CUID
• PROFJOB_CUIDUSER
• PROFJOB_CUID_SCHEME
• PROFJOB_CUID_SCHEME_ANALYTE

The archive can include custom user tables that exist in the CCLAS database. The archive/retrieve fails if there is an error archiving one of these custom tables. This is a security mechanism to ensure that all the required user-defined records are included as part of the whole archive/retrieve process.

The records from the custom tables are deleted if the job is removed as part of the archive process.

Custom tables must have a LABCODE and PRO_JOB field, and must be join to the PROFJOB table.

{DatabaseTableName}

The user account used to access the destination database.

{DatabaseUser}

The folder where the XML files created as part of the archive process are written.

{FolderName}

The folder where CCLAS archived job ZIP files are located.

Example: %CCLASRootDirectory%ARCHIVE

{FolderName}

When a rack and mode is selected in the Data Entry application:

• If enabled, then the auditing of the selected schemes and analytes is reduced to a single row per scheme.
• If disabled, then the auditing of the selected schemes and analytes includes one row per analyte in the scheme.

Enabled | Disabled

Where the AutoStoreFormattedValue global setting is enabled, when the On-line, Data Entry, Job or Analytical Report application writes values into the FinalValue field, thereby forcing the calculation and storing of the FormattedValue field:

• If enabled, then the changes to the formatted value are audited.

Enabled | Disabled

If any of these functions are specified, then only those functions are audited when they are run in the Data Entry application.

If no functions are specified, then all functions are audited when they are run in the Data Entry application. These include:

• SAVE
• BYE/QUIT
• REPORT
• NEXT
• REGRESSION
• INSTRUMENT
• STOP INSTRUMENT
• START INSTRUMENT
• EDIT INSTRUMENT
• AVG
• LETVAR
• SETVAR
• VSET
• ALPHA

SAVE | BYE | FORCE | INSTRUMENT, or a comma-delimited list of these functions.

If enabled, then the writing to the Quality Control History table occurs automatically.

Enabled | Disabled

If any of these QC failure or check statuses are specified, then only those QC failures or checks set by the Data Entry or On-line applications are audited. Note that this is applied regardless of whether AuditInitialUpdates is enabled or disabled.

If no QC failures or check statuses are specified, then all QC failures or check statuses set by the Data Entry or On-line applications are audited.

QFH | QFL | QFT | CHK, or a comma-delimited list of these QC failure and check statuses.

If enabled, then all changes to PJCSA fields by the Data Entry or On-line applications are audited.

If disabled, then all changes to PJCSA fields by the Data Entry or On-line applications are audited, except for where a result is first entered into the empty field.

Enabled | Disabled

When a result is stored by the Data Entry or On-line application:

• Where PJCSA fields are specified, then audit records are only written for changes to those fields.
• Where no PJCSA fields are specified, then audit records are written for changes to all updated fields.

FINALVALUE | ANALYTESTATUS, or a comma-delimited list of fields.

When concentration result records are created for the job:

• If enabled, then the date activated is updated with the system date, and thereby available for laboratory batching.
• If disabled, then jobs are not manually activated, and thereby unavailable for laboratory batching until they are activated.

Enabled | Disabled

If enabled, jobs and schemes are marked automatically with a status of Completed based only upon analytes that are flagged as Status Active. If no analytes in a scheme are flagged as status active, then the schemes are marked automatically with a status of Completed as soon as the job is started.

Enabled | Disabled

If enabled, then jobs are marked automatically as completed when their schemes are completed.

Enabled | Disabled

If enabled, and the AutoLogoutCCLAS program setting is also enabled, when a user exits the CCLAS menu or logs out via any CCLAS program, then their slot in the Licence table is set to Not in use. This enables other users to use that licence to log into CCLAS.

This setting is typically used when the maximum number of concurrent users is less than the maximum number of non-concurrent users, as defined by the CCLAS licence at the site.

Enabled | Disabled

If enabled, then preparation schemes are marked automatically as completed when the job is started.

Enabled | Disabled

If enabled, where an UNK, REP, DUP or reread sample has product limits defined, when a result is received that is within the product limits and the result pass any QC checks, then the analyte status is set to complete (CPL).

Note that when using final mode in the Manual Data Entry grid, then product limit checking is only performed on numeric values. Otherwise, product limit checking is performed when values are saved.

For example, when using raw mode and formula values, then the real status is not visible on the Manual Data Entry grid until the values are saved and the grid is closed and opened in final mode.

The On-Line application does product limit checking when a result is saved.

Enabled | Disabled

If enabled, when the analytes for the scheme are completed, then schemes are marked automatically as completed.

Enabled | Disabled

If enabled, when data is entered in the On-line or Data Entry application, then the formatted value of the result is stored automatically. This enables programs that write values into FinalValue to also calculate and store the FormattedValue.

Enabled | Disabled

When results are reported:

• If enabled, then the conversion factor between the analysis and reporting units is automatically applied.
• If disabled, then CCLAS presumes that any variations between analysis and reporting units are only represented by the header column names.

Enabled | Disabled

The default average priority assigned to a new client, measured in days or hours, depending upon the value of the PriorityUnit setting.

The local currency used, based upon the codes specified in the InvConversion table, accessed from the Invoice Conversions item in the Setup application. Ideally, the conversion factor for this code in the InvConversion table is 1.

{CurrencyUnit}

The folder where various temporary CCLAS files are located.

Example: %CCLASRootDirectory%Bin

{FolderName}

If enabled, then the formatted values for sample results are calculated and stored automatically.

Enabled | Disabled

The URL of the Internet Explorer application.

Example: C:\Program Files\Internet Explorer

{URL}

The root folder where the <IMCCC> folders are located. This logical name is used to refer to folders below the root directory.

Example: \\servername\CCLAS

\\{ServerName}\{CCLASRootFoldername}

The name of the laboratory's certifying officer.

{Text}

The title of the laboratory's certifying officer.

{Text}

The character used by controls in all CCLAS applications.

Example: 128

{CharacterSet}

If enabled, when a numeric final value is saved by the Online or Data Entry application, then a check is made as to whether the result is less than the analytical detection limit, in which case, a less-than-detection-limit (<DL) figure is shown on a report of the result.

Enabled | Disabled

When a numeric result is compared to the analytical detection limit:

• If enabled, then the comparison against the detection limit occurs after the result is rounded.
• If disabled, then the comparison against the detection limit occurs before the result is rounded.

Enabled | Disabled

The folder where collated output files (reports, etc.) are located.

Example: %CCLASRootDirectory%Coll

{FolderName}

The name of the company.

{Text}

The folder where configuration files are located.

Example: %CCLASRootDirectory%Config

{FolderName}

The folder foot where CCLAS executable files are located.

Example: %CCLASRootDirectory%Exe\

{FolderName}

The font used by controls in all CCLAS applications.

Example: Arial Unicode MS

{FontName}

The font size used by controls in all CCLAS applications.

If enabled, when formulas are displayed in the Data Entry application, then the formulas are displayed using regional settings.

Enabled | Disabled

The folder where CCLAS help files are located.

Example: %CCLASRootDirectory%Help

{FolderName}

The name of the CCLAS help file accessed from within CCLAS applications, located in the folder defined by the %HelpDirectory% global setting.

{FileName}

The folder where CCLAS icon files are located.

Example: %CCLASRootDirectory%Icons

{FolderName}

The folder where CCLAS sample ident files are located.

Example: %CCLASRootDirectory%Idents

{FolderName}

The folder where CCLAS instrument data files are located.

Example: %CCLASRootDirectory%IFFScripts

{FolderName}

If enabled, then weekends are included in the calculation to determine sample date and time required, etc.

Enabled | Disabled

The default invoice message placed on an invoice template.

{Text}

The name of the laboratory.

{Text}

If enabled, when a laboratory batch job is created, then scheme-specified REP and SPK samples are added to the laboratory batch job, even if the job already has RRD or REP samples from the component client jobs.

Enabled | Disabled

The job number used for laboratory batch creation.

{UniqueNumberSeq}

When a laboratory batch job is created, then schemes and analytes are copied from the specified template job.

{TemplateJobNumber}

If enabled, when a laboratory batch job is created, then an NA status on an analyte in the client job is copied into the laboratory batch job, and replicates and reread samples created in the laboratory batch job have the NA status applied to the related analytes.

Enabled | Disabled

If enabled, when the On-line or Data Entry application stores a weight or volume for a laboratory batch job, then these values are copied automatically to the client job. This allows for the viewing of the raw results from the client jobs.

Enabled | Disabled

The number of days a warning is given that the site's CCLAS licence is about to expire.

The folder where CCLAS login script files (menus, etc.) are located.

Example: %CCLASRootDirectory%Login

{FolderName}

If a file name is defined, then login and logout events are written to this file.

If the file name is not defined, but the Global Setting LoginOutNTEventLog is enabled, then events are written to the NT Event Log file on non-Win 95/98 computers .

Example: %CCLASRootDirectory%BinDirectory\LoginOutEvent.log

{FileName}

If enabled, where the file name supplied by LoginOutEventLogFile is not defined, then login and logout events are written to the NT Event Log file on non-Win 95/98 computers.

Enabled | Disabled

The number of times a staff member can enter an incorrect password before the account is disabled. Once disabled the account cannot be used for login purposes and needs re-activation by an authorised staff member.

The folder where CCLAS Data Entry script files are located.

Example: %CCLASRootDirectory%MDEScripts

{FolderName}

The folder where CCLAS method documents files are located.

Example: %CCLASRootDirectory%Methods

{FolderName}

Denotes how blank samples are applied in a pro-rata manner.

When quality control samples are added to a block of samples for a scheme, and the scheme's Blank calculation is selected as PRO, when the scheme's Number Blanks is applied to the sample group denoted by the scheme's Blank blocksize, if MinimumProRataBLK is set to:

• One/Block -Then at least one blank sample is allocated to each sample group denoted by the specified block size. For example, where the Blank blocksize is 40, and Number blanks is 2, then at lease one blank sample is applied per 40 samples.
• Zero - Then blank samples are allocated as specified by the scheme used to batch the samples. For example, where Blank blocksize is 40, and Number blanks is 2, then one blank sample is allocated each group of 20 samples.
• One/Segment - Then at least one blank sample is allocated to each proportional set of samples within the sample group denoted by the specified block size. For example, where Blank blocksize is 40, and Number blanks is 2, then one blank sample is allocated to the first group of 20 samples and one blank sample is allocated to the second group of 20 samples, effectively calculated as 20 (40 Samples / 2 Blanks = 20 Samples per proportional set of samples within the sample group).

One/Block | Zero | One/Segment

Denotes how replicate samples are applied in a pro-rata manner.

When quality control samples are added to a block of samples for a scheme, and the scheme's Replicate calculation is selected as PRO, when the scheme's Number Replicates is applied to the sample group denoted by the scheme's Replicate blocksize, if MinimumProRataREP is set to:

• One/Block -Then at least one replicate sample is allocated to each sample group denoted by the specified block size. For example, where the Replicate blocksize is 40, and Number replicates is 2, then at lease one replicate sample is applied per 40 samples.
• Zero - Then replicate samples are allocated as specified by the scheme used to batch the samples. For example, where Replicate blocksize is 40, and Number replicates is 2, then one replicate sample is allocated each group of 20 samples.
• One/Segment - Then at least one replicate sample is allocated to each proportional set of samples within the sample group denoted by the specified block size. For example, where Replicate blocksize is 40, and Number replicates is 2, then one replicate sample is allocated to the first group of 20 samples and one replicate sample is allocated to the second group of 20 samples, effectively calculated as 20 (40 Samples / 2 Replicates = 20 Samples per proportional set of samples within the sample group).

One/Block | Zero | One/Segment

Denotes how spike samples are applied in a pro-rata manner.

When quality control samples are added to a block of samples for a scheme, and the scheme's Spike calculation is selected as PRO, when the scheme's Number Spikes is applied to the sample group denoted by the scheme's Spike blocksize, if MinimumProRataSPK is set to:

• One/Block -Then at least one spike sample is allocated to each sample group denoted by the specified block size. For example, where the Spike blocksize is 40, and Number spikes is 2, then at lease one spike sample is applied per 40 samples.
• Zero - Then spike samples are allocated as specified by the scheme used to batch the samples. For example, where Spike blocksize is 40, and Number spikes is 2, then one spike sample is allocated each group of 20 samples.
• One/Segment - Then at least one spike sample is allocated to each proportional set of samples within the sample group denoted by the specified block size. For example, where Spike blocksize is 40, and Number spikes is 2, then one spike sample is allocated to the first group of 20 samples and one spike sample is allocated to the second group of 20 samples, effectively calculated as 20 (40 Samples / 2 Spikes = 20 Samples per proportional set of samples within the sample group).

One/Block | Zero | One/Segment

Denotes how standard samples are applied in a pro-rata manner.

When quality control samples are added to a block of samples for a scheme, and the scheme's Standard calculation is selected as PRO, when the scheme's Number Standards is applied to the sample group denoted by the scheme's Standard blocksize, if MinimumProRataSPK is set to:

• One/Block -Then at least one standard sample is allocated to each sample group denoted by the specified block size. For example, where the Standard blocksize is 40, and Number standards is 2, then at lease one standard sample is applied per 40 samples.
• Zero - Then standard samples are allocated as specified by the scheme used to batch the samples. For example, where Standard standards is 40, and Number standards is 2, then one standard sample is allocated each group of 20 samples.
• One/Segment - Then at least one standard sample is allocated to each proportional set of samples within the sample group denoted by the specified block size. For example, where Standard standards is 40, and Number standards is 2, then one standard sample is allocated to the first group of 20 samples and one standard sample is allocated to the second group of 20 samples, effectively calculated as 20 (40 Samples / 2 Standards = 20 Samples per proportional set of samples within the sample group).

One/Block | Zero | One/Segment

The folder where CCLAS note files (methods, scheme details, etc.) are located.

Example: %CCLASRootDirectory%Notes

{FolderName}

The number of days for which a warning is given by the system to a staff member that their password is about to expire.

If set to 0, then no warning is given by the system.

The minimum number of characters for a valid password.

If set to 0, or absent, then there is no minimum length required.

If enabled, then password controls are used to ensure more security on setting passwords, based on PasswordReuseRejectCount and PasswordReuseRejectRange.

If disabled, no additional security is placed on setting passwords.

Enabled | Disabled

The count, based upon the PasswordReuseRejectRange, that defines the period for which a password cannot be reused. Where PasswordReuseRejectRange is set to:

• DAYS - Then the PasswordReuseRejectCount sets the number of days within which a password cannot be reused.
• TIMES - Then then PasswordReuseRejectCount sets the number of times within which a password cannot be reused.

If 0, or absent, then no reuse checking is applied.

Indicates whether the reuse of old passwords is based on a date range or on a number of times range.

If set to NONE, or absent, then no password reuse is checked.

NONE | DAYS | TIMES

The folder where various CCLAS picture files are located.

Example: %CCLASRootDirectory%Picture

{FolderName}

The folder where various pre-configured CCLAS files are located.

Example: %CCLASRootDirectory%PreCreated

{FolderName}

The unit in which priority is applied. if set to:

• Days - Then due dates and times are calculated by adding priority to the date received.
• Hours - Then due dates and times are calculated by adding priority to the time received.

Hours | Days

If enabled, when schemes are added to a job using a procedure, the price code comes from the scheme in the procedure and not from the scheme itself.

Enabled | Disabled

The colour of the background of fields that are read-only.

{Colour}

If enabled, QC History records are updated.

Enabled | Disabled

The folder where CCLAS quality control files are located.

Example: %CCLASRootDirectory%QControl

{FolderName}

The default method of calculating percentage difference between an original sample and a duplicate or replicate QC sample:

• 1 = Normal - The percentage difference is calculated using the difference between the original UNK sample's result and the replicate sample's result. (The default mode.)

  Percentage Difference = Absolute (R1 - R2) / R2 x 100

• 2 = Average - The percentage difference is calculated using the average of the original UNK sample's result and the replicate sample's result.

  Percentage Difference = Absolute (R1 - R2) / Average (R1 + R2) x 100

In these formula, R1 is the original sample's result and R2 is the duplicate or replicate sample's result.

The folder where CCLAS report files (e.g., Crystal Reports) are located.

Example: %CCLASRootDirectory%Report

{FolderName}

If enabled, then final reports contain non-validated data.

If disabled, then reporting of such data is blocked.

Enabled | Disabled

When a report using the Crystal Reports engine is generated in the Analytical Report application, the PJCSA result set is sorted alpha-numerically ascending using defined field. The PJCSA.REPSEQUENCE field cannot be used as a sort by field.

Example: PJCSA.CUID

PJCSA.{FieldName}

The folder where CCLAS laboratory run files are located.

Example: %CCLASRootDirectory%RunList

{FolderName}

The source of the text from the original sample used to populate the PJC.DESCRIPTION field for a spike sample.

After all the specified fields are used to populate the spike sample's description, if the string is longer than the length of the PJC.DESCRIPTION field in the database, then the text is truncated.

Example: When a sample with a sample ident of ABC and an external ident of DEF is spiked:

• Where theSpikeDesIDSource is set to [PJC.EXTERNALIDENT], then the spike sample is allocated a description of DEF.
• Where the SpikeDesIDSource is set to [PJC.SAMPLEIDENT,PJC.EXTERNALIDENT], then the spike sample is allocated a description of ABCDEF.

PJC.{FieldName}[,PJC.{FieldName}][,...]

Selected from [PJC.SAMPLEIDENT], [PJC.EXTERNALIDENT], [PJC.DESCRIPTION].

The source of the text from the original sample used to populate the PJC.EXTERNALIDENT field for a spike sample.

After all the specified fields are used to populate the spike sample's external ident, if the string is longer than the length of the PJC.EXTERNALIDENT field in the database, then the text is truncated.

Example: When a sample with a sample ident of ABC and an external ident of DEF is spiked:

• Where theSpikeExtIDSource is set to [PJC.EXTERNALIDENT], then the spike sample is allocated an external ident of DEF.
• Where the SpikeExtIDSource is set to [PJC.SAMPLEIDENT,PJC.EXTERNALIDENT], then the spike sample is allocated an external ident of ABCDEF.

PJC.{FieldName}[,PJC.{FieldName}][,...]

Selected from [PJC.SAMPLEIDENT], [PJC.EXTERNALIDENT], [PJC.DESCRIPTION].

The font used by screen caption, menu, message box and tool tips in all CCLAS applications.

Example: Arial Unicode MS

{FontName}

The font size used by screen caption, menu, message box and tool tips in all CCLAS applications.

The folder where various CCLAS VBScript files are located.

Example: %CCLASRootDirectory%Tasks

{FolderName}

The folder where CCLAS template files are located.

Example: %CCLASRootDirectory%Templates

{FolderName}

The folder where CCLAS tip files are located.

Example: %CCLASRootDirectory%Tips

{FolderName}

If enabled, after SampleDelete or SampleAdd (that is, AddSampleToConcDB) is performed, then the ident files (that is, the IDS, EID, DES and PRD files) are rebuilt (either internally or externally based on the UseIdentsFiles global setting).

Enabled | Disabled

If enabled, when a sample weight is captured for a parent scheme, then the weights of samples in linked schemes are updated automatically with the same weight.

Enabled | Disabled

If enabled, when the date and time received or required are changed. then the job's priority is updated automatically.

Enabled | Disabled

When a request is made to create or re-create the analytical result records (ProfJob_Cuid_Scyheme_Analyte) records for a job (with update NOT being selected):

• If enabled—A bulk insert is used to create the records. A bulk insert process is slower for smaller jobs, but an advantage for large ones with lots of schemes and analytes.
• If disabled—The analytical result records are created in the normal way.

Enabled | Disabled

When a request is made to create or re-create the analytical result records (ProfJob_Cuid_Scyheme_Analyte) records for a job (with update NOT being selected):

• If enabled—The transaction is performed in a transaction (Begin Trans ... End Trans), allowing for roll-back upon any failure in the database process.

Enabled | Disabled

When idents are stored:

• If enabled—All internal idents are written to an IDS file in the Idents directory.
• If disabled—Where an IDS file does not exist in the Idents directory, and the size of the IDSFILE field in the ProfJob table is large enough to hold all of the characters, then all internal idents are written the idents field, comma-separated. Where an IDS file exists, then the file is used instead of the field/s.

Similarly for EID, DES, PRD and EXC content.

Enabled | Disabled

If enabled, then the password the user uses to log into Windows is also used to log into CCLAS.

Enabled | Disabled