Microsoft KB Archive/126863

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 18:12, 20 July 2020 by X010 (talk | contribs) (Text replacement - ">" to ">")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Delivery Point Bar Code Uses 99 in Last Two Digits of Address

Q126863



The information in this article applies to:


  • Microsoft Word for Windows, versions 6.0, 6.0a, 6.0c





SYMPTOMS

When you use Word's Delivery Point Bar Code option when printing envelopes, Word uses 99 for the last two digits of the street address. This may happen if you use the BARCODE field in a mail merge main document or if you use literal text in the field code.



CAUSE

This error occurs when the syntax for the field code is incorrect. When the syntax is incorrect, Word cannot correctly parse the string for the delivery-point information. Whenever Word cannot correctly determine the delivery-point information, it prints 99.



RESOLUTION

Literal Text

The correct syntax for the BARCODE field code when you use literal text to generate the field code is:

   {BARCODE "123 Oak Street<paragraph mark>
   98052-6399"\u  } 

The paragraph mark tells Word how to correctly parse the string for the delivery-point information.

Mail Merge

The structure of the field code is the same as for literal text, but the address information is generated by two merge fields

   {BARCODE "{mergefield street}<paragraph mark>
   {mergefield zip}"\u  } 

where "mergefield street" is the merge field that contains the street address and "mergefield zip" is the 5+4-digit ZIP Code for the address.



MORE INFORMATION

There are three different types of bar codes: the 5-digit bar code, the ZIP+4 bar code, and the delivery point bar code.

The following is an example of a 5-digit bar code using literal text:

   {BARCODE "12345" \u} 

The following is an example of a ZIP+4 bar code using literal text:

   {BARCODE "12345-6789" \u} 

Additional query words: 6.0 winword word6

Keywords : kbfield
Issue type :
Technology :


Last Reviewed: November 4, 2000
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.