[AccessD] Membership File Changes

Reality is I'm an old timer and the solution worked for me.  I'm a happy camper!

Jim Barrett - Timpson, TX



>________________________________
> From: John W Colby <jwcolby at gmail.com>
>To: Access Developers discussion and problem solving <accessd at databaseadvisors.com> 
>Sent: Thursday, March 6, 2014 6:43 PM
>Subject: Re: [AccessD] Membership File Changes
>  
>
>This strategy is not without detractors however, mostly "old timers" from databases where multi-field PKs were ALWAYS used. Mostly they try to argue that it is possible to just read the PK down in the child / grandchild / great grandchild etc. simply by looking at the data in the multi-field PK, which "saves your bacon" when orphans creep in and so forth.  Additionally the "values" can often be pulled for reporting and the like, without requiring joins back up the chain.  Both are true, but not (IMO) make up for the overhead and headaches that multi-field PKs bring with them.
>
>
>John W. Colby
>
>Reality is what refuses to go away
>when you do not believe in it
>
>
>