[AccessD] Design Question

IIUC, then I would do two tables - Members and External Organizations with a 
linking table containing the PKs from both.  That assumes that many Members 
could be contacts for the same External Organization and one External 
Organization can have many members as contacts.

Rocky

----- Original Message ----- 
From: "Josh McFarlane" <darsant at gmail.com>
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Sent: Sunday, November 13, 2005 9:38 PM
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
>