The Barcode component cannot read one of the supported barcode types.
This can happen in one of the following cases:
The search zone does not include the area where the barcode is located.
Using the image that contains the barcode as a sample, change the search zone so that it includes the barcode.
If you are not sure that this location is always going to be the same for all images,
then increase the zone or add another zone or do not use a search region, and the component will try to find the barcode on the entire page.
The search zone includes barcode area, but the page where the barcode is located is excluded from page recognition.
If you use images in which barcodes are located on the same pages, then configure recognition for all necessary page numbers.
If you are not sure if this location is always going to be the same for all images then select
option Recognize zone on all pages.
The barcode is read but does not satisfy validation criteria.
In this case set more flexible criteria or set No validation option.
Insufficient quality of barcode recognition.
For better recognition results specify as much barcode information as possible. In particular it is recommended
to specify exact orientation, to select zone more precisely and to select the Require exactly one barcode in the zone check box.
Error in component script causes component to hang.
You can insert On Error Resume Next in a routine to continue a function
and avoid hanging the application processing should an error occur in a
script. For more information about using On Error Resume Next, see the
following MSDN references:
The search returns topics that contain terms you enter. If you type more than one term, an OR is assumed, which returns topics where any of the terms are found. Enclose your search terms in quotes for exact-phrase matching.
The search also uses fuzzy matching to account for partial words (such as install and installs). The results appear in order of relevance, based on how many search terms occur per topic. Exact matches are highlighted.
To refine the search, you can use the following operators:
Type + in front of words that must be included in the search or - in front of words to exclude. (Example: user +shortcut –group finds shortcut and user shortcut, but not group or user group.)
Use * as a wildcard for missing characters. The wildcard can be used anywhere in a search term. (Example: inst* finds installation and instructions.)
Type title: at the beginning of the search phrase to look only for topic titles. (Example: title:configuration finds the topic titled “Changing the software configuration.”)
For multi-term searches, you can specify a priority for terms in your search. Follow the term with ^ and a positive number that indicates the weight given that term. A higher number indicates more weight. (Example: shortcut^10 group gives shortcut 10 times the weight as group.)
To use fuzzy searching to account for misspellings, follow the term with ~ and a positive number for the number of corrections to be made. (Example: port~1 matches fort, post, or potr, and other instances where one correction leads to a match.)
Note that operators cannot be used as search terms: + - * : ~ ^ ' "
