[AccessD] Another normalization question

This is the approach I would take.

Create a Phone number table and assign the number to whom / wherever it is needed using the key.

Cheers
Darryl



-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bill Benson
Sent: Wednesday, 17 September 2014 5:45 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Another normalization question

I read recently a phone number table with FkPhoneType .... and I want to say also, a FKBusinessEntityId. I am pretty sure i saw this in a sql server sample database called adventureworks. I could be wrong, but I liked it.
That way a single phone number table works for all classes of entity (people, and institutions).
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com