Bobby Heid
bheid at appdevgrp.com
Thu Apr 28 07:06:13 CDT 2005
Ok, I think I understand your issue now. Sorry that my first try was so far off. I did something similar with an address book thingy for this application. A given entry could be primary contact on one item, payroll contact on another, etc. So that I did not have to duplicate the people data, I used an intermediate table to store links to the people data. There is a table of contact information for each person. There is another table that contains the ID of the record that will be associated with the person. This other table also contains the ID of the person in the people data table, An example: Table Main MainID Contact ClosedBy ReleasedBy 3 43 49 49 Intermediate table IMID MainID PersonID 43 3 754 49 3 29 People Table PersonID FirstName LastName 754 Joe Schmoe 29 Suzy Chapstick So you would store the IMID into the Main table for the various contacts. The intermediate table would contain a link to the Main table and the People table. The People table just contains information on the individual people. So to get the Contact person, you would link the ContactID to the Intermediate table IMID and then link the PersonID in the Intermediate table to the PersonID in the People table. In this way, you are not duplicating the People data. Bobby -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hollis,Virginia Sent: Thursday, April 28, 2005 7:41 AM To: accessd at databaseadvisors.com Subject: [AccessD] Table of Names Yes, the name of a person can fit into any or all categories. The Contact, Closedby, ReleasedBy, etc call all be the same person. ************ Virginia, I could be wrong, so take this with a grain of salt -- but it sounds like Contact, IssuedTo, IssuedBy, ClosedBy, ReleasedBy are categories that describe each person. Before we go any further, would a "name" entity have more than one category? Susan H.