Code 128 Barcodes created with Crystal UFL or Windows DLL not scannable
Affected products are 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 issue only occurs in these products and does not occur in any other fonts or functions.
Solution(s):
Problem Detail:
The Crystal Reports UFL is a legacy product that should only be used when other options are not available. In the latest IDAutomation font packages, a Crystal Report example with a Font Encoder Formula is provided in the package for easy integration. IDAutomation recommends using the Font Encoder Formulas instead of the UFL.
If this UFL is necessary, 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.