[AccessD] Number vs text data type

Hello Gustav,

This has been an interesting discussion, to say the least, but I have to say
that I do appreciate that the US Government is not likely to suddenly do an
overnight change to the postal code system. It's just that everybody got
hooked on talking specifically about Zip codes which is why I said that "the
point is that the Zip code is just an *example* of a number that's not
really an number at all."

As it turns out, Cynthia was talking about exactly the kind of "private"
identifiers that can get changed on a whim by shortsighted managers. :-)

Lambert

> -----Original Message-----
> From:	Gustav Brock [SMTP:gustav at cactus.dk]
> Sent:	Thursday, October 16, 2003 5:06 AM
> To:	Access Developers discussion and problem solving
> Subject:	Re: [AccessD] Number vs text data type
> 
> Hi Lambert
> 
> I think you are mixing up two things here.
> 
> Private formats controlled by some management may, of course, be
> changed with no warning.
> 
> Public formats, however, are so widely used that you'll always be
> given a lead time counted in years. This holds true for postal code
> formats, telephone number formats etc.
> 
> Have for example a look at how slowly but steadily the IBAN
> international numbering format for bank accounts is promoted while
> you still, but at increasing costs, can use the old system with bank
> names, BIC (SWIFT) codes and account numbers.
> 
> But I will vote with you.
> 
> /gustav
> 
> 
> > Drew,
> 
> > True the (US) post office may or may not be planning a zip code reorg,
> but
> > the point is that the Zip code is just an example of a number that's not
> > really an number at all.
	  <snip>