[AccessD] Slow day - normalization discusion

It would be consistent but is it necessary.  Depends somewhat on whether it
will be all U.S. numbers.  Given the wide variety of formats in phone
numbers around the world, more and more I find that a free form text field
for the phone number is easier on the users, unless you intend to do some
reporting and sorting on the phone number.

I'd stick with the first scheme, myself.

Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com
www.bchacc.com
 
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bartow
Sent: Wednesday, June 18, 2008 8:35 AM
To: 'Access Developers discussion and problem solving'
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

No virus found in this incoming message.
Checked by AVG. 
Version: 8.0.100 / Virus Database: 270.4.0/1507 - Release Date: 18/6/2008
07:09