Specifications

Configuration
11
this Tag File Prefix value. Changing this value in the Profile will not
affect the tag file names in existing tag sessions.
Duplicate
Tag Codes
This setting determines what to do in the event a duplicate tag code
is detected during data collection. It is highly recommended to use
the 'Prompt user for choice' value for this setting, which notifies
the user of the duplicate tag event and prompts them to take one of
four actions.
The other values for this settings will bypass the notification prompt
and automatically invoke a particular action
for the duplicate tag
code event. These automated actions are useful in situations when
multiple tag readers are sending large amounts of redundant
information to the application.
Auto
Accept
When the Auto Accept setting is set to 'Yes', individual Tag Detail
Records are processed and written to disk automatically when the
next tag code is read from a device
. Auto Accept will not override
any program or user-defined validation routines that might detect
an error or alert condition and prevent processing. In such an event
the new tag code, and any subsequent input, will be stored in the
Tag Code Buffer
until the current record has been completed and
manually processed.
Verbose
Species
Run and
Rear
If this setting is set to 'Yes', a single, verbose description will be
used in place of the species, run and rearing-type
codes throughout
the entire application (with the exception of the search
and replace
features). If it is set to 'No', single-character codes are used to
identify the species, run and rearing-type values throughout the
application.
Note: Verbose descriptions are limited to only common
combinations of numeric codes. If a verbose description does not
exist for a particular combination, the numeric combination of
species run and rearing-type codes will be displayed instead.
Mandatory
Length
If the Mandatory Length setting is set to 'Yes', a tag detail record
cannot be processed until a valid length (or Dash-Out
) value is
entered into the field.
Mandatory
Weight
If the Mandatory Weight setting is set to 'Yes', a tag detail record
cannot be processed until a valid weight (or Dash-Out
) value is
entered into the field.
Data
Logging
Setting this value to 'Yes' will write a comma separated line of data
for each new or edited detail record to an external file described in
the Log File setting below.
Tip: Logged data can be easily recovered from a file using the
Import CSV Wizard.
Log File This setting designates the log file to be used for logging any new
or edited detail records, if the Data Logging setting described
above is enabled.
Note: The log file may reside on a floppy drive to ensure data
recovery in the case of a hard disk failure. However, logging to the