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
P3 Help
102
When the Type of Code selection is set to 'Verbose Species, Run and Rear Codes',
the Delete command button will permanently remove one or more selected codes.
This may be useful for restricting the number of codes displayed in the Species Run
and Rear tag detail field (verbose mode only). Removing these validation codes
applies for all tag sessions and is not associated with any profile.
Note: The verbose validation codes will be refreshed each time the validation codes
are updated; you will need to remove any verbose codes each time the validation
codes are updated.
Database Maintenance
As you delete objects (e.g., tag sessions or dot-out records) in the application, the
application's internal database can become fragmented and use disk space
inefficiently. The database maintenance tool makes a copy of the database file and
rearranges how the file is stored on your disk; this usually results in a much smaller
file size. This command should be run periodically to ensure optional performance.
To access this tool, select the Database Maintenance command located under the
Tools menu. The command will display a prompt to confirm running this command;
once the maintenance process starts, it may take several minutes and cannot be
stopped. This tool makes a copy of the original database and places it in the
../P3/Temp directory.
Note: Before running this utility, make sure there is adequate disk space available-
at least double the size of the p3.mdb file.