Scanner Testing

In that a 'keyboard wedge' or USB scanner operates in effect like another keyboard, it's quite easy to test.

Open Notepad on your computer.

Scan labels.

See what the scanner is reading.

If the scanner doesn't read reliably, try adjusting the Barcode line width in Program Preferences. You can also experiment with whether your scanner reads Code 39 or Code 128 more reliably. (ForScore's default is to use Code 39.)

It will be useful for you to be aware of the encoding scheme ForScore uses for labels. This is done so that the software can distinguish a stage data entry label, for example, from a shooter's IDPA number label.

There are four formats used:

1.	Labels with shooter number and stage number (either for pre-registered shooters, including their names and other info, or generic club match labels with just shooter number and stage number.)

•	If these are printed with a 'carriage return', the format is

%ShooterNumber+StageNumber$.

•	If printed without a 'carriage return', the $ character is not printed.

2.	Labels with shooter number only (for matches like Classifiers where all stages are on one sheet of paper.)

•	Printed with a 'carriage return' they are $ShooterNumber$.

•	Without a 'carriage return' they are $ShooterNumber.

3.	Labels with a shooter's IDPA number begin with a +.

•	With 'carriage return' you would see +A12345$.

•	Without, +A12345.

•	NOTE: if you see lower case letters (i.e., a12345), disable Code 39 full ASCII.

4.	Labels for equipment or chrono check begin with // (two slash marks)

•	With 'carriage return' you would see //ShooterNumber$.

•	Without, //ShooterNumber.

Using Notepad, sample scans would appear like this (minus my comments, obviously :-) )