OHM-Stat CT-8900 Owner's Manual page 36

name, first name, and id#
2. If the person is not found in the EsdTest data base, then look up the person's badge number in the Remote data base.
If the person is found there, then get the //////////////person's ID number from the remote data base, and search the
EsdTest data base for the person's id#
a. if it already exists then update that person's badge number in the EsdTest data base
b. else add the person to the EsdTest data base
3. If the employee is not found in the remote data base either, and if the Unknown employee setup window is configured
to accept unknown employees (see adding unknown employees in the main help file), then the employee may key in
his name and be added to the Esdtest data base.
4. Otherwise the employee will be rejected and not allowed to test.
5. If recognized, the employee may then proceed with the test, and the test data is stored in the EsdTest log.txt data
base, and/or a remote log data base (see Remote test data base help file)
6. The Esdtest data base can be later exported back to the remote data base if desired
Method 2 – Only use the remote data base and never use the EsdTest Names.txt file data base. Note that this method will prohibit
using most of the EsdTest report features, and will only function as long as the network and remote data base server are functioning.
Editing the employee information from the EsdTest program can only be done by another copy of the EsdTest program running in
Method 1, 3, or 4 and importing the entire remote data base into the EsdTest Names.txt file, editing it, then exporting back to the
remote data baser. What this feature does is:
Testing sequence
1. When a person swipes his badge, look up the badge number in the Remote data base and retrieve the last name, first
name, and id#
2. If the person is not found in the EsdTest data base, then the employee will be rejected and not allowed to test.
3. If recognized, the employee may then proceed with the test, and the test data is stored in the EsdTest log.txt data base,
and/or a remote log data base (see Remote test data base help file)
Method 3 – Use the remote data base, but keep a local copy of it to use if the network or server stops functioning. Note that this
method will prohibit using the EsdTest sick/vacation report features. What this feature does is:
Testing sequence
1. On program boot, copy the entire remote data base to the EsdTest Names.txt file data base. Note that this overwrites all
the previous data and clears all sick and vacation data.
2. When a person swipes his badge, look up the badge number in the remote data base. If the person is not found in the
remote data base, then the employee will be rejected and not allowed to test.
3. If the person is found in the remote data base, then update the EsdTest data base if that person is not already in there.
4. If the remote data base or network is unavailable, then look up the employee in the EsdTest Names.txt file data base. If
the person is not found in the remote data base, then the employee will be rejected and not allowed to test.
5. If recognized, the employee may then proceed with the test, and the test data is stored in the EsdTest log.txt data base,
and/or a remote log data base (see Remote test data base help file)
REMOTE DATA BASE CREATION
Create a view with a name like ESD_EMP_BADGE_VW to the company data base with the following fields:
LAST_NAME (will be holding data like - Smith)
FIRST_NAME (will be holding data like - Fred)
BADGE (will be holding data like - 3852)
DEPT (will be holding data like - CIA)
EMPID (will be holding data like - 12345)
WRIST_USED (will be holding data like - 0 or 1) this field is not required
FOOT_USED (will be holding data like - 0 or 1) this field is not required
CERTIFICATION_EXPIRATION_DATE (will be holding data like - 10/28/2006) this field is not required
It may be best to have all fields be text (char) fields, although the CERTIFICATION_EXPIRATION_DATE field can be a date field.
Static Solutions CT-8900 Combo Tester Instructions 36 7/22/2009