I print lot's of form letters and I've have found that
the barcode generator in Word is inaccurate when it comes
to hi-rise buildings so the only way around this is to
use our existing data but when it's plugged into the
barcode field all we get is an error message...
This is my response to a similar question:
----------------------------------------------
As far as I am aware (unfortunately I cannot easily test here) Word will
generate the full 11 digit Postnet bar code but the last two digits of the
11-digit code are typically derived from a street address, which needs to be
part of your BARCODE field.
So you typically need a BARCODE field that looks like:
{ BARCODE "{ MERGEFIELD "street address" }
{ MERGEFIELD Postcodefield }" \u }
Where the Postcodefield contains a ZIP code in 5-4 format (with the hyphen).
However, the last 2 digits may not be generated from a Street address in all
cases, so you may need to do something more than just { MERGEFIELD "street
address" }. You may find the following articles useful:
WD2000: How to Read Postal Bar Codes
http://support.microsoft.com/default.aspx?scid=kb;en-us;214181
and the article referenced in there:
WD2000: USPS Changes Postal Bar Code Requirements for Multi-Unit Buildings
http://support.microsoft.com/default.aspx?scid=kb;EN-US;220548
The barcode field inserted by the Envelopes/Labels option uses a
slightly different approach which is to bookmark the whole address and use
{ BARCODE bookmarkname \b \u }
I would have also have a look at:
WD97: Word Assigns a Delivery Point Bar Code (DPBC) of 99:
http://support.microsoft.com/default.aspx?scid=kb;en-us;197008
----------------------------------------------
FInally, my guess is that if you can create two fields in your data source,
one with the final two dgits of the 11-digit barcode and one with the first
9 in the format 12345-6789, then use the first of those fields as the
"Street address" field in your BARCODE field, you will /probably/ get the
output you need. But I really don't know for sure. Also, it wouldn't
surprise me if you had to add a fake street name to the number to give you
22 Fake Street
to get it to work.
How you create those fields depends on your data source. If your data is in
Access, it should be fairly easy to create a query that splits the ZIP field
up and provides the two fields you need. Even with text files it may be
fairly straightforward, but I would first want to confirm that the basic
approach suggested above actually generates the correct barcodes, then work
out how to split up the field.
--
Peter Jamieson - Word MVP
Word MVP web site http://word.mvps.org/
"Wes" <anon...@discussions.microsoft.com> wrote in message
news:ff9d01c40d89$0ab17860$a401...@phx.gbl...
I read the articles reference by our MVP and I don't know
where (or when might be a better focus) Microsoft got
their info from the USPS but we are now discontinuing the
use of Word in favor of another product that will use the
DPBC generated by our postal certified software. The pay
up on a 80,000+ piece mailing that failed to pass MERLIN
was over $2000; it doesn't take many of those to pay for
$8000 software product that will generate the right
barcode.
On the other hand, it would be nice if Word would accept
the 11 digit DPBC generated by mailer software.
Perhaps another option for Word users is to purchase a
font package. You would still need to insure they keep
up with the continuing evolving USPS standards.
Good luck!
>.
>
Get a quality barcode font. Here you can find Morovia U.S. Postal Font package:
www.morovia.com/font/usp.asp