Re: Storing Telephone Numbers

I've hit this issue too.  Given the lack of standards, maybe the best
thing to do is take data in whatever format a user gives it to you,
then learn from the database what common masks are used in various
locations.  Finally apply regional masks to data that doesn't match
the mask of the region, but where the number of digits is right.  You
can get a head start by looking at existing directories of published
data sorted by region.  The rules are frequently as the user
themselves define the rules...

Tony

[EMAIL PROTECTED] (CWNoah2) wrote:

>Is there a table anywhere of different country formats which could be used with
>country code to provide output formatting of stored raw numbers?
>
>Regards,
>Charlie Noah
>
>Kevin Powick <[EMAIL PROTECTED]> writes:
>
>>[EMAIL PROTECTED] says...
>>
>>> How many of you store
>>> phone numbers as a 7 or 10 digit number (string) and then format the number
>>> for display or how many store the formatted number
>>
>>I generally designate fields for country code, city/area code, local 
>>number, and extension.  This probably covers most situations and allows 
>>you to assemble/format the output as you see fit.  MS Outlook uses this 
>>approach (minus the extension field) and I think it works pretty well.
>>
>>I don't force formatting because many international numbers don't 
>>follow a North American (nnn) nnn-nnnn format.  However, the only field 
>>that I allow non-numerics (dash, dot, and space) is the local number.
>>-- 
>>Kevin Powick
>
>
>Charlie Noah ([EMAIL PROTECTED])