[AccessD] International Addresses
newsgrps at dalyn.co.nz
Thu Nov 11 16:58:14 CST 2021
In my case it is just a physical address they are storing so that
technicians know where to go for servicing.
There are different fields used for sorting and filtering locations so that
is covered separately.
Rocky's idea of having them set up the label names for the fields seems to
be the most flexible since most users will only have addresses for a single
From: AccessD <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com> On
Behalf Of Stuart McLachlan
Sent: Friday, 12 November 2021 11:11 am
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] International Addresses
There are no internalonal common ways to represent addresses.
You should be aware that household/business delivery is rare or
non-existent in many places, so depending on purpose, you may need to store
both a mailing address and a physical address which may be in different
suburbs or even towns.
What is the purpose of storing the data. Do you want to be able to
It's often best to use a single multi-line field as Address, then have
separate Town/City, State/Province, Country fields.
If you use Address1, Address2, Address3 etc you will almoste certainly end
up with some records with Country in Address 3 and others with Country in
Address 4 or 5 etc. making reporting an absolute PITA.
On 12 Nov 2021 at 9:45, David Emerson wrote:
> Hi Listers,
> I am writing a system that potentially could be used globally. I am
> looking for guidance on how to handle storing address fields. At this
> stage the data is just to record site addresses and probably (famous
> last words) will not be used for mailouts as most of the sites will be
> Should I just use a simple structure such as AddressLine1,
> AddressLine2, AddressLine3, Addressline4, AddressLine5 or is there a
> more elegant way of doing it?
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
More information about the AccessD