Native Crystal Reports User Manual

NOTE: This product supports Crystal version 9 and later. Refer to
the Crystal Integration
Guide for products that support earlier versions.
Legal Notice: This product is
Patented. Reports containing this object may only be distributed
outside the licensed organization with the purchase of a Developer License
to the Native Barcode Generator.
The Native Barcode Generator is an object that may be easily inserted
into a Crystal Report to create barcode images. Once installed in a
report, no other components or fonts need to be installed to create
barcodes; it is the complete barcode generator that stays with the report,
even when distributed.
The Crystal Reports Native Barcode Generator supports
the following symbologies:
The following barcode symbologies may be created upon request
with the purchase of the Unlimited Developer License:
- Code 93
- Intelligent Mail (AKA OneCode)
Installing the Native Barcode Generator is a fairly simple process.
Several generators are created for different barcode types.
- Extract the files from the Native Barcode Generator package.
- Several generators are created for different barcode types.
Open the report that represents the bar code type that is needed.
If in doubt, IDAutomation recommends choosing Code 128 Auto, which
is in the file named IDAutomation
Native - Code 128 Auto.rpt.
- Choose View - Design to switch to design mode and locate the
Native Barcode Generator on the report.
- Highlight the Native Barcode Generator object and choose Edit
- Copy. The Native Barcode Generator object is the first field in
the details area that contains very small text.

- Open the report the barcode is needed for and choose Edit -
Paste to paste the Native Barcode Generator object where it is desired.
- When using Code 128 and
GS1-128 (UCC/EAN-128), the text object just below the Native
Barcode Generator object should also be copied, if it is desired
to have the text interpretation appear below the barcode.
- Highlight the object and choose Edit - Edit Formula.
- Modify the "DataToEncode ="
line of the formula to equal the data that is to be encoded in the
barcode.

If an error such as "A string is required" appears, the data
will need to be converted to a string with a crystal function. For
example: DataToEncode = cStr( {Table1_.FloatValueField},0
)
- Optionally, variables below the "DataToEncode
=" line of the formula may be changed as necessary.
- When changing the "BarHeight =" variable, the size of the
object must also be increased so that taller barcodes may be
contained. The approximate height is determined with the following
formula:
Height in Inches
= (Font Size) * (BarHeight) * 0.015 Height in CM
= (Font Size) * (BarHeight) * 0.04 For example, the
default BarHeight of 8 equals about 0.3 inches and 1 centimeter.
- If it is necessary to change the X dimension or barcode width,
highlight the object and change the font point size. The point size
must be small, generally 3 or 4 points. Because the drop down box
does not contain these small sizes, they must be manually typed
in. The font selected for the object must be "Courier New" or another
mono-spaced unicode font.

|
Point Size
|
Approximate
X Dimension
|
| 2 |
08 Mils |
| 3 |
12 Mils |
| 4 |
16 Mils |
| 5 |
20 Mils |
| 6 |
24 Mils |
| 7 |
28 Mils |
| 8 |
32 Mils |
- Run the report to verify barcodes are being properly created.
Ensure the object has been sized properly to contain the entire
barcode. If the width of the symbol is larger then the object, several
white lines will appear.

- Print the report to verify that the barcodes are created properly
and that they can be scanned with a scanner. If a scanner is needed
to verify barcodes, IDAutomation offers several
affordable, barcode
scanner kits including
plug-and-play
USB scanners.
- It is normal to view some distortion of the symbol on the screen
because of low screen resolution. However, the barcodes should be
accurate when printed.

Common Problems and Solutions:
- If scanning problems are encountered, verify a printer
of 600 DPI or greater is being used. A large point size
such as 5 points must be used with low resolution printers.
IDAutomation also offers many barcode fonts that
print well to low resolution printers.
- Ensure the barcode can fit in the object. If the width
of the barcode is larger then the object, several white
lines will appear.

- The font selected for the object should be "Courier
New," "Lucida Console" or another mono-spaced Unicode font.

A proportional font may also be used for some linear barcode
types, however it is not recommended. If a proportional
font is used, change MonoSpaceFont = True to MonoSpaceFont
= False in the formula.
- If several small question marks appear instead of a
barcode when creating a PDF for performing other conversions
of the report, it is an indication that the component performing
the conversion is not
Unicode compliant. In this situation, contact the component
vendor to obtain an updated or
Unicode compliant
version.
- In the event white lines appear in the barcode, highlight
the object and choose Format - Field - Paragraph. Adjust
the line spacing to the largest size that eliminates white
lines in the symbol. Generally, the setting of 0.8 to 0.95
is used for the "Courier New" font.

- The Data Matrix and PDF417 Generators provided in the
2D version may generate slowly because of the complex algorithms
used in these symbologies. IDAutomation recommends encoding
50 characters or less when using these symbologies. More
data may be encoded, although the report may take longer
to generate. To quickly generate 2D barcodes in Crystal
Reports, use the supplied UFL in the IDAutomation
Data Matrix Font and Encoder or the
PDF417 Font and Encoder.
- If an error such as "A string is required" appears,
the data will need to be converted to a string with a crystal
function.
For example:
DataToEncode = cStr( {Table1_.NumberField1},0 )
Additional problems and solutions are provided on the
barcode font troubleshooting page and by searching resolved
public forum threads.
Priority phone, email and forum support is provided up to 30 days
after purchase. Additional
priority phone, email and forum support may be obtained with an
active Priority
Support and Upgrade Subscription.
Back to Top
|