Why can't ReadBAR read
just any barcode?
Reading a barcode image successfully depends on the resolution
of the image, the skew amount, and how many pixels are between
the bars. The ReadBAR component is optimized to read known barcodes
in known locations, as determined by the developer of the system.
For indexing purposes in document imaging, a code 3of9 barcode
is the best solution and is tolerant of misalignment and poor
image quality. ReadBAR can be optimized for fast reading.
Will ReadBAR automatically
find the bar code?
Sort of - the goal is not to find any barcode anywhere on the
page, but to find a particular barcode in a known location, on
a separator sheet or data input form. ReadBAR can start at the
uppermost location of the barcode and step down into the barcode,
rereading it until it finds a valid code or runs out of space.
This almost always finds the barcode quickly and optimizes throughput..
How good do the images
have to be?
ReadBAR is designed to work well with less than perfect images.
It is helpful to use a checkdigit to validate the barcode for
indexing purposes, or to check each barcode against a database.
The goal is to be able to scan images at 200 DPI reliably
How can I be sure the
barcode is right?
Generally the nature of the 3of9 barcode is that it will either
return a valid number or no answer at all. Naturally a clean,
straight image is best, but ReadBAR can handle considerable skew
(15 degrees or more) and still return accurate results. If you
are producing the barcode to begin with, you can use a check digit
to prove that the barcode read correctly. It is quite difficult
to return an answer which is wrong but reads right.
What I want to know
is ... ?
Send us your questions and comments
and we'll see what we can do for you.
Return to Delphi developers
components main page >