[AccessD] Slow day - normalization discusion

...I suspect what you are looking at is a design implemented in the days 
when area code changes were becoming common place and this design addresses 
that particular need and nothing else.

...I have to deal with thousands of foreign numbers which have to be 
formatted precisely in order to take advantage of the automated dialing in 
fax systems among other needs ...that requires a much more sophisticated 
format and validation lest the client get cops showing up at his door in 
response to his trying to send a fax to a 911 area code in India.

...but if the current format you have meets all your client's current and 
probable future needs, I'd leave it be ...breaking out the 3 digits in the 7 
digit local number tells you nothing these days ...unlike the old days a 708 
exchange number can be next door to a 402 and thus no longer conveys any 
useful data beyond the number itself.

William
"Sen. McCain will bring a lifetime of experience to the campaign...  Sen. 
Obama will bring a speech that he gave." Hillary Clinton

--------------------------------------------------
From: "John Bartow" <john at winhaven.net>
Sent: Wednesday, June 18, 2008 11:35 AM
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Subject: [AccessD] Slow day - normalization discusion

> I recently had pull data from a contact mgt. app's database where the
> normalization brought up a question in my mind. The phone information was
> normalized as:
>
> tblPhone:
> fldPhoneID (PK)
> fldPhoneTypeID (FK)
> fldAreaCodeID (FK)
> fldPhoneNumber
> fldPhoneExtension
>
> tblPhoneType:
> fldPhoneTypeID (PK)
> fldPhoneType
>
> tblAreaCode:
> fldAreaCodeID (PK)
> fldAreaCode
>
> To be consistent with this level of normalization wouldn't it make sense 
> to
> have the first three numbers separated from the back 4 numbers? The first
> three would be very repetitious also. So the table would appear as:
>
> tblPhone:
> fldPhoneID (PK)
> fldPhoneTypeID (FK)
> fldAreaCodeID (FK)
> fldPhoneNumberPrefixID  (FK)
> fldPhoneNumber
> fldPhoneExtension
>
> tblPhoneType:
> fldPhoneTypeID (PK)
> fldPhoneType
>
> tblAreaCode:
> fldAreaCodeID (PK)
> fldAreaCode
>
> tblPhonePrefix:
> fldPhoneNumberPrefixID  (PK)
> fldPhoneNumberPrefix
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com