[AccessD] OT: The Great Primary Debate

In the strictest sense that may be true because you now have more than
one unique key on the table, but since "candidate" keys are acceptable
in relational design, I wouldn't worry about that myself.  And if you
have a single field unique key, that is always preferable to a compound
unique key as a PK, since it is easier to manage and doesn't require
inserting multiple FK fields into another table.

Charlotte Foust

-----Original Message-----
From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] 
Sent: Thursday, June 03, 2004 7:28 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] OT: The Great Primary Debate


Gustav:

I think you are fooling with me..:-) ...and do you know that for sure?

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gustav Brock
Sent: Thursday, June 03, 2004 12:56 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] OT: The Great Primary Debate


Hi Jim

> Lambert: Your are right of course...always keep the client happy and 
> in
this
> case what they do not know will not hurt you.

Except that you will be denormalizing your schema!

/gustav

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