Mail Merge in MS Publisher 2003

[E. J. ROZEK]

How can one properly format a Postnet field for a mail
merge? Microsoft Word uses the function
{ BARCODE "{MERGEFIELD ZIP }"\u }
which formats the 5- or 9-digit zip code into a proper
Postnet bar code with first and last frame bar,
correction character and omits spaces and hyphens.
Publisher 2003 doesn't seem to accept this function.
Simply using a Postnet type font for the zip code will
not add frame bars, correction character and includes
space and hyphen.

 

[Brian Kvalheim - [MS MVP]]

Hi E. J. ROZEK ([email protected]),
in the newsgroups
you posted:

|| How can one properly format a Postnet field for a mail
|| merge? Microsoft Word uses the function
|| { BARCODE "{MERGEFIELD ZIP }"\u }
|| which formats the 5- or 9-digit zip code into a proper
|| Postnet bar code with first and last frame bar,
|| correction character and omits spaces and hyphens.
|| Publisher 2003 doesn't seem to accept this function.
|| Simply using a Postnet type font for the zip code will
|| not add frame bars, correction character and includes
|| space and hyphen.

This is not a feature of Publisher.

--
Brian Kvalheim
Microsoft Office Publisher MVP
Official Publisher MVP Site:
http://www.kvalheim.org

This posting is provided "AS IS" with no warranties, and
confers no rights.

 

[Mike Koewler]

E. J.,

You need to use a program that will take an address and convert it to a
12-digit barcode. (Nine digit zip code, two digit county code and one
digit checksum.) Some of these are cheap, some are expensive. You can
then import this data into your mail merge field and set the font to a
postal bar code font but the font size has to be 12 point. But it won't
help if you do not supply supporting data that your addresses are
correct, at least in the US.

Mike

 

[Massmailer maybe]

I have been tryign to determine whether the MSWord barcode function will generate the full 64 bar code required for Postal carrier routing, one of the cheapest rates. My list processir will CASS certify the information...but I can't be sure the mail merge will work...ie create the 64 bar code. Any help of this would be appreciated.

 

[Massmailer maybe]

I have been tryign to determine whether the MSWord barcode function will generate the full 64 bar code required for Postal carrier routing, one of the cheapest rates. My list processir will CASS certify the information...but I can't be sure the mail merge will work...ie create the 64 bar code. Any help of this would be appreciated.

 

[Matrix]

I've been struggling with a postal bar code problem, also. After posting my question to the newsgroup, I did some additional research and saw your entry below. Did you ever find a way around this? I am specifically trying to incorporate zip plus 4 bar codes into a Publisher 2003 document. I do have the cleaned up address info and the zip code field in my data source already contains the xxxxx-xxxx zip code. I just can't find a way for Publisher to translate this supplied data into the bar code itself

----- E. J. ROZEK wrote: ----

How can one properly format a Postnet field for a mail
merge? Microsoft Word uses the functio
{ BARCODE "{MERGEFIELD ZIP }"\u
which formats the 5- or 9-digit zip code into a proper
Postnet bar code with first and last frame bar,
correction character and omits spaces and hyphens.
Publisher 2003 doesn't seem to accept this function.
Simply using a Postnet type font for the zip code will
not add frame bars, correction character and includes
space and hyphen

 

[Matrix]

I've been struggling with a postal bar code problem, also. After posting my question to the newsgroup, I did some additional research and saw your entry below. Did you ever find a way around this? I am specifically trying to incorporate zip plus 4 bar codes into a Publisher 2003 document. I do have the cleaned up address info and the zip code field in my data source already contains the xxxxx-xxxx zip code. I just can't find a way for Publisher to translate this supplied data into the bar code itself

----- E. J. ROZEK wrote: ----

How can one properly format a Postnet field for a mail
merge? Microsoft Word uses the functio
{ BARCODE "{MERGEFIELD ZIP }"\u
which formats the 5- or 9-digit zip code into a proper
Postnet bar code with first and last frame bar,
correction character and omits spaces and hyphens.
Publisher 2003 doesn't seem to accept this function.
Simply using a Postnet type font for the zip code will
not add frame bars, correction character and includes
space and hyphen