Robert Stewart
rls at WeBeDb.com
Fri May 27 15:02:38 CDT 2011
Primary Key = Nothing a user can use for anything and is totally not dependant on data. For db system use only Business Key = Something within the data that is unique and can be used by a user for identification. Business Keys can be one or more fields, when more than one, it is a Composite Business Key. Remember the above and you will not have any issues. Example: tlkp_NameSuffix NameSuffixID Autonumber NameSuffix Text(30) NameSuffixID is the primary key NameSuffix is the business key, and has a unique index on it. Robert L. Stewart www.WeBeDb.com www.DBGUIDesign.com www.RLStewartPhotography.com At 01:18 PM 5/27/2011, you wrote: >Date: Fri, 27 May 2011 08:18:47 -0500 >From: "Dan Waters" <df.waters at comcast.net> >To: "'Access Developers discussion and problem solving'" > <accessd at databaseadvisors.com> >Subject: Re: [AccessD] [Spam]8.31 Re: 2 quick questions >Message-ID: <001101cc1c70$9d48a380$d7d9ea80$@comcast.net> >Content-Type: text/plain; charset="us-ascii" > >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 > >