Kath Pelletti
KP at sdsonline.net
Mon Nov 14 16:04:22 CST 2005
That's a great one - perfect for lots of businesses which struggle with family level and personal data etc. Kath ----- Original Message ----- From: MartyConnelly To: Access Developers discussion and problem solving Sent: Tuesday, November 15, 2005 3:52 AM Subject: Re: [AccessD] Design Question Here is a data model example using people and roles People in households and companies - modelling human relationships http://allenbrowne.com/AppHuman.html Susan Harkins wrote: >I'm with William on this one. I'd have just one table of people and use >another table to track their roles. > >Susan H. > >...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. > > > > > -- Marty Connelly Victoria, B.C. Canada -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com