Specifications
Table Of Contents
- Overview
- Configuration
- Configuration Profiles
- General Profile Settings
- Configuring Devices
- Activating Tag Actions
- Validation Constraints
- Audible Alert Sound Events
- Data Collection and Validation
- Importing and Exporting
- Tools
- Tag Actions
- Tag Action Manager
- Tag Action Settings and Commands
- Tip: the Replace command will import tag codes much faster than the Import command. Use the Import command only when appending a relatively small number of tag codes (less than 25k) to a tag action.
- Tip: the Delete All and Replace commands will generate a lot of empty space in the P3 database. We recommend running the Compact and Repair utility after running any of these commands to optimize the database.
- Tag Actions and Data Entry
- Digitizer Maps
- Searching Data
- Replacing Data Values
- Merging Tag Sessions
- Dot-Out Wizard
- Remove Dot-Outs
- Duplicate Viewer
- Validation Codes
- Database Maintenance
- Tag Actions
- Appendix
- Frequently Asked Questions
- Hardware Support
- Troubleshooting Common Tag Reader Problems
- Troubleshooting Common Digitizer Tablets Problems
- Digitizer Tablet Doesn't Register Pen Clicks
- WinTab Digitizer Tablet Won't Communicate with a PC
- ASCII Digitizer Tablet Won't Communicate with a PC via Serial Port
- Digitizer Tablet doesn't Communicate with P3
- Digitizer Tablet is Sending the Wrong Commands
- Digitizer Tablet is Sending Wrong Lengths
- Digitizer Tablet Hangs P3 when Connected via Baytech Multiport
- Operating the Destron 400 kHz Benchtop Tag Reader
- Configuring Calcomp Drawing Board III
- Index
Data Collection and Validation
45
Code field and resets the detail record
for new input.
Replace Automatically scrolls to the detail record
containing the first instance of the
duplicate Tag Code. The user can edit
the other detail fields in that record.
Dot Out The original detail record containing the
duplicate tag code is automatically
dotted-out
. The current detail record will
contain the new tag code and the user
can continue entering data into the other
fields.
Accept Accepts the duplicate tag code and
allows the user to continue processing
the detail record. This method can be
used when the user wants to dot-out the
previous instance of the tag code and
also wants to annotate the record with a
comment explaining the dot-out.
Tag detail records containing duplicate
tag codes are displayed on the Statistics
viewer. All detail records containing
duplicate tag codes must be resolved
(each duplicate converted to a Dot-Out)
before a tag session is considered valid.
VRT Code
Assignments
All VRT codes must have a variable release date and time
assigned
to them before the tag session is considered to be
valid. Also, all of the release header fields
must be
completed.
Tag Session Commands
This topic describes commands specific to data entry and validation of the tag
session. These commands are grouped together under the Session menu heading
and some can also be found on one of the tool bars. Most of these commands can be
associated with a digitizer map
and called from a tablet device.