Dan Waters
df.waters at comcast.net
Fri May 27 08:18:47 CDT 2011
A field with an 'Intelligent Key' is fine - as long as you don't use it in a table relationship. In other words, always have an arbitrary (autonumber, etc.) key as the key that is used in table relationships. That way you'll NEVER have to spend hours or days rebuilding tables when the key you used in a dozen or more table relationships is changed. Dan PS - Even RFID's can be swapped out, and Tattoos can be removed! -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Friday, May 27, 2011 1:06 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] [Spam]8.31 Re: 2 quick questions Intelligent Keys are an excellent concept when you can attach them to the item concerned or to it's container. Unless you can tattoo them or implant an RFID chip, there is little point in trying to use IKs to identify people. :-) -- Stuart On 27 May 2011 at 1:55, Arthur Fuller wrote: > I don't know where you obtained this rule against the use of > Intelligent Keys, but I seriously object, and cite Chris Date and > Fabian Pascal and the inestimable Joe Celko for reasons why IKs are a > good thing, in certain applications (eggs are a bad example; car parts > are an excellent example). > > A. > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com