[AccessD] Primary Key Best Practices

There are lots of tables that do not require a PK.  Any table without
children.   


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 John Bartow
Sent: Wednesday, July 25, 2007 6:27 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Primary Key Best Practices

OK now I think YOU'RE talking theoretically :o)

What purpose would a one table database serve? And if there is a purpose
would it even be considered relational? Sure I created spreadsheets that
could be called databases but not by me, because I always mentally preface
database with relational. I personally refer to a spreadsheet database as a
list to avoid confusion.

But all that aside I think we mostly agree on things here - it mostly
nitpicky terminology/theory that some of us don't agree on.

Yes or No:
Have you ever created a one table relational database? (OK, smart alecs -
that remained so.) Have you ever created a table that didn't have a PK?
(when you were done creating it)

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Wednesday, July 25, 2007 4:47 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Primary Key Best Practices

Any database made up of a single table would not require a PK. 

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