|
If its a thousand, can it be 9,999 ? That becomes quite a few PO Boxes. --------------------------------- Booth Martin http://www.martinvt.com --------------------------------- -------Original Message------- From: Midrange Systems Technical Discussion Date: 05/04/05 14:20:27 To: Midrange Systems Technical Discussion Subject: RE: Normalization was Left AS/400 and Returned Make that 1000+ PO boxes. Stupid el-cheapo keyboard... John A. Jones, CISSP Americas Information Security Officer Jones Lang LaSalle, Inc. V: +1-630-455-2787 F: +1-312-601-1782 john.jones@xxxxxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jones, John (US) Sent: Wednesday, May 04, 2005 1:58 PM To: Midrange Systems Technical Discussion Subject: RE: Normalization was Left AS/400 and Returned Regarding zip+4, the extra 4 digits can also be a PO box number (PO Box 102 would be represented by xxxxx-0102). I don't know if the USPS refrains from overlap between street addresses and PO boxes or not. I don't see how it logically can, since it's not too dificult to have 100+ PO boxes in a single zip. And a zip that large would likely have many unique addresses as well. So do rural routes/stops impact this discussion as well? Maybe it's just plain easier to store c/s/z. Plus, it probably makes storing international addresses in the same db easier as they should map to city/province/postal code. John A. Jones, CISSP Americas Information Security Officer Jones Lang LaSalle, Inc. V: +1-630-455-2787 F: +1-312-601-1782 john.jones@xxxxxxxxxx This email is for the use of the intended recipient(s) only. If you have received this email in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this email without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. The information contained in this communication may be confidential and may be subject to the attorney-client privilege. If you are the intended recipient and you do not wish to receive similar electronic messages from us in the future then please respond to the sender to this effect. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. .
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
