[AccessD] One-to-One relationships

<Listen to the data>
Or hire a Data Whisperer to do it for you :-)
Jim Hale

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Friday, July 20, 2007 7:46 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] One-to-One relationships

Yes, if it has a purpose. A one-to-one relationship almost always flows
from
need rather from the data itself. If you need to force a one-to-one, I'd
say
do it. However, if there's no business rule saying, "there can be only
one..." it might be unnecessary, even if the data is presenting that
picture
right now. Listen to the data. 

Susan H. 

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?  


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

***********************************************************************
The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or
other use of or taking action in reliance upon this information by
persons or entities other than the intended recipient is prohibited.
If you have received this email in error please contact the sender and
delete the material from any computer. As a recipient of this email,
you are responsible for screening its contents and the contents of any
attachments for the presence of viruses. No liability is accepted for
any damages caused by any virus transmitted by this email.