[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

----- Original Message ----- 
From: "Josh McFarlane" <darsant at gmail.com>
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Sent: Monday, November 14, 2005 12:38 AM
Subject: [AccessD] Design Question


> Hey guys got a quick question about design.
>
> I'm making a database for a non-profit service organization I'm
> working for. There's going to be membership data per person, however,
> at the same time the person may be a contact to an external
> organization for part of their projects, or it may be some completely
> unrelated person.
>
> Here's my question:
>
> Should I have only one table, called say People, or should I have two
> seperate tables of data: Members and Contacts?
>
> Option A would require intermediate tables linking anything to the
> people table, but Option B would maintain duplicate data for members
> that are also in external contact organizations.
>
> Any suggestions?
>
> Thanks!
> --
> Josh McFarlane
>
> "Peace cannot be kept by force. It can only be achieved by understanding."
> -Albert Einstein
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>