[AccessD] One-to-One relationships

In your example, maybe, maybe not.  I have a database where there is a claim
table and three different "extension" tables which are 1 to 1 with the claim
table.  TblClaimSTD is for short term disability claims, and stores
information specific to short term claims.  There is also a (you guessed it)
tblClaimLTD for long term disability and stores all the claim information
specific to long term claims.  There is a third table tblWP or waiver of
premium where claim waiver of premium information is stored.  In all these
cases there is a rather large table with information that is in every claim,
and then one of those three "extension" tables with information about one of
those three specific types of claims.

1-1 tables require special handling in entering data as well as displaying /
reporting the data.  Whether it is worth doing is a question that bears
asking in any specific case.


John W. Colby
Colby Consulting
www.ColbyConsulting.com 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Barbara Ryan
Sent: Thursday, July 19, 2007 7: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