[AccessD] Design Question

Yea, William just prides himself on being different.  I didn't want to break
the news to him...

;-)

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Monday, November 14, 2005 11:34 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Design Question


That sounds pretty much like the way I do it too.

Charlotte Foust


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Hindman
Sent: Monday, November 14, 2005 4:54 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Design Question


...as usual, I do it a bit differently ...master table for "entity" with an 
ID, and type ...one to one child tables for orgs and persons using the 
entity ID ...then build a many to one role table as child to the master in 
which the entity can show in several different roles without denormalizing 
the relationships or data ...then you can show the person's role in both

internal and external orgs ...hope that makes sense.

William

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com