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
90
such as 'Records where Conditional Comment contains M'. The condition that
logically combines one or more Elementary Conditions is called a Complex
Condition, such as 'Select records where any of the following apply'. A search can
have one or more Complex Conditions. To add or delete a condition, click the
button.
Elementary Conditions
When creating an Elementary Condition, there are three statement components
that must be defined: Field, Comparison and Value.
Clicking on the Field modifier will display a drop-down list of all available fields from
a tag session, grouped by Tag Session Header
, Tag Detail and Variable Release
Times.
The Comparison modifier defines how the Field and Value modifiers will be
related. This modifier can be 'Equal', 'Greater', 'Less', 'Greater or Equal', 'Less or
Equal', 'Not Equal', 'Is Empty', 'Is Not Empty', 'Contains', and 'Starts With'. The last
two modifiers, 'Contains' and 'Starts With', can only be used with text fields.
If the Comparison modifier is set to something other than 'Is Empty' or 'Is Not
Empty', then the user must supply a Value. A list box will automatically appear so
you can choose an item from pre-defined field domains. For fields without pre-
defined domains of values (such as the Length, Weight, and Textual Comments
fields) you can key in the comparison value. For text fields you can use a "%"
wildcard to match any group of characters or a "_" wildcard to match any single
character within the text value.
Advanced Elementary Conditions
The primary use of the Advanced Elementary Conditions statement is to compare the
contents of two fields. For example, to find all differences between the Session
Name and Tag File values, your statement would be "Records where field
Session
Name is not equal to field Tag File".
Complex Conditions
When defining a Complex Condition, click on the blue hyperlinked word to select a
modifier. The modifier determines how all elementary conditions are logically
connected to produce the result set: