Some Code 128 barcodes do not scan when using the Crystal UFL or Native Windows DLL
The products affected are the Code 128 Barcode Fonts that use Code128Auto Functions and UCC128 Functions in the Crystal UFL and the Native Windows Font DLL distributed from June 2005 to September 1, 2005 with file names and dates as follows:
U25IDAutomation.dll 6-22-2005 or any date before September, 2005 IDAutomationNativeFontEncoder.dll 7-08-2005 or any date before September, 2005
This problem only occurs in these products and does not occur in any
other fonts or functions.
| Solution(s): |
Problem Detail:
Under rare conditions, certain barcode data will not return the correct check digit, therefore creating an incorrect barcode that will not scan. To reproduce this problem, encode the following data with the Code 128 Auto function:
Ê00180329860300003191
The data returned should be:
ÍÊÂ2#=v#ÂÂ?{ÂÎ
However, if the data returned is:
ÍÊÂ2#=v#ÂÂ?{Î
Then the problem exists in the component.
To obtain the update, please download the latest version from the links below.
| Related Documents and Keywords: |
See also:
- Unable to scan data printed with a barcode font
- Last character of TrueType font is not printing properly or is truncated
- The TrueType font is installed but is not printing properly - TrueType font problems in Windows
- Font displays symbols instead of the actual font
TSI
|
Product Quick Links: [ Barcode Fonts | Font Tools | Components | Label Software | Scanners | Printers | RFID ] |
Copyright ©
2000-2006 IDAutomation.com, Inc.
IDAutomation and BizFonts are registered trademarks of IDAutomation.com,
Inc. All other
trademarks mentioned are the property of their respective owners.
|
Over 70% of Fortune 100 companies use IDAutomation's products to automate their businesses. |