Troubleshooting barcodes

Barcode design

To ensure that barcodes are interpreted correctly, the designers of the code check for errors on several levels:

Generally speaking, the newer barcode types are better and safer.

For more information, see Optimal design of barcode fields.

FORMS’ interpretation of barcodes

If an error is detected (for example, if a checksum or symbol is incorrect or start/end bars are missing), the total result for the field is considered to be invalid, and the field value is represented by an asterisk (*) during verification.

Barcodes do not have to be perfectly straight on the form. However, it must be possible to draw a horizontal line (relative to the bottom of the page) through the barcode that intersects the entire barcode. (Example.)

FORMS imposes limitations on the length of certain barcodes. In addition, there are limitations in the interpretation of certain barcodes. See Barcodes supported by FORMS for more information.

Note: Your format specification for the barcode field is not used during interpretation. It is used as an extra check after interpretation.

If the barcode is not being interpreted at all

Ensure that the form definition does not include an actual barcode. Normally a blank form is used to set up the form definition. If there is a barcode in the barcode field as you define it, then you must erase the barcode. The general procedure is:

  1. Deactivate the form definition.

  2. Delete the barcode field definition.

  3. Erase the barcode from the field area.

  4. Redefine the barcode field.

  5. Save and reactive the form definition.

See Editing an active form definition and Erasing marks from forms if you prefer more detailed instructions.

Suggestions for improving interpretation of barcodes

Important: If there is a barcode on the form as you define it (normally a blank form is used to set up the form definition), then you must erase the barcode. Otherwise, the barcode will not be interpreted. Follow the instructions in Erasing marks from forms.