Postnet Bar Code

rbuser

Hi,

The post office seems to have an issue with the vertical height of the
smallest bar in the printing of a postnet barcode.
The USPS specifies it should be between 0.04" and 0.06". It appears that it
prints it at about 0.08".

Can anyone point me in the right direction for making an adjustment to the
height?

--
Isaac Culver

nicocizik

Hi Shelila,

Is is possible to adjust the TppBarCode.Height property to get the results
you need? If not, check out the following article on adding your own
barcodes to ReportBuilder.

----------------------------------------
Article: Adding new BarCode types
----------------------------------------

ReportBuilder natively supports the following barcode types:

- Codabar
- Code 128
- Code 39
- EAN-8
- EAN-13
- Interleaved 2 of 5
- PostNet
- UPC-A
- UPC-E


Options for adding new BarCode types:


Find a VCL or ActiveX BarCode component that supports the desired BarCode
type. Adapt the component for use in RB in one of the following ways:

a. Use the third-party BarCode component to export the barcode output to an
image and then use RB's Image component to print the barcode.

b. Write a ReportBuilder "wrapper" component that adapts the third-party
component to work inside the RB Designer. This is the approach used to
integrate the TeeChart component within RB. A "wrapper" component is a
descendant of RB's TppCustomComponent that instantiates and uses a
third-party component to implement the desired rendering. See ppChrt.pas in
the RBuilder\Source directory for an example.


We have had customers use both of the above techniques successfully....

--

rbuser

nicocizik

Hi Gary,

If possible, please send a small example to support@digital-metaphors.com
that prints a Postnet barcode incorrectly so I can test it with my printer
and perhaps code a solution to the issue.

--

rbuser

nicocizik

Thanks Gary, I'll do some testing here and get back to you as soon as
possible.

--

rbuser

nicocizik

Hi Gary,

Thanks for bringing this to my attention. After a little more research, I
found that this issue has been addressed and fixed in RB 7. Thanks for your
patience and help.

--