[AccessD] One-to-One relationships

Definitely, IMO, especially in databases where you may have different
kinds of customers.  For example, a business and a non-profit and an
individual and a family group could all be customers, but would have
differing kinds of information.  Using one-to-one relationships, you
could have a single Customer table that had the minimum information that
would be collected on all customers, regardless of type.  Then you could
have a separate table for Organization and one for Persons.  The PK in
each of those tables would be inherited from the Customer table.  This
would also allow you to have other tables with common information
hanging off the customer table instead of the Organization or Persons
table.  You might want to hang the Address table off Customers, for
example, since addresses are fairly consistent.

Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Barbara Ryan
Sent: Thursday, July 19, 2007 4:51 PM
To: Access List
Subject: [AccessD] One-to-One relationships

Is there any purpose/advantage in creating a one-to-one relationship in
a database (e.g., CustomerId and CustomerName in one table and all the
other customer data (e.g., sex, address,  phone, etc) in another table?


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