[AccessD] One-to-One relationships

Barb,

Not in the example you gave, no.  Given that you will be recording sex, 
address, phone for all, or almost all, of the customers.

The main use for one-to-one relationships is in a sub-typing scenario. 
This is where you have data where there are some data in common for 
all/most records, but there are also fields required specific to certain 
categories of the main data.

Regards
Steve

Barbara Ryan wrote:
> 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?