[AccessD] Membership File Changes

<snip>
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.
</snip>

John, I was recently called an old timer because I insisted on using
autonumber integer PK for some of our new designs.
The young whipper snapper said that's the "old way" of doing things, and is
very anal about using GUIDS and multi-field PKs.

I know GUIDs have their place, but he just doesn't get it. I love how my
stuff runs so much faster, even with joins. :)

D