[AccessD] Primary Key Best Practices

I anm digging a deep hole for this one.

Looking out from stuff flying from JC's mountain fortress of code.

-----Original Message-----
>From: Jim Hewson <JHewson at karta.com>
>Sent: Jul 24, 2007 7:55 AM
>To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
>Subject: [AccessD] Primary Key Best Practices
>
>I need a few good references (preferably electronic) on the Best
>Practices for defining Primary Keys (PK)
>Here at the office we have had a few heated discussions about primary
>keys.
>I don't' mean to stir the pot on this list, just curious what others
>think.
>
>1.  All tables should have a primary key even though it will not be used
>as a foreign key (FK) in another table.
>2.  PKs should always be an autonumber (Access), Identity (SQL) or GUID.
>3.  Avoid complex PKs such as two PKs from two other tables.
>4.  Avoid complex PKs such as two fields from one table.
>
>You could probably come up with some more.
>
>Thanks,
>
>Jim H. 
> 
>
>-- 
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com