Reply to thread

Message: [QUOTE="John Vinson, post: 2549737"] Names are NOT UNIQUE. I once worked with Dr. Lawrence David Wise and his colleague, Dr. Lawrence David Wise. They do *not* make good keys! In addition, people change their names (on marriage or for other reasons). This can be handled with cascading updates, but this makes for added complications (e.g. prior payments made under one name will show up under the new name). I would very strongly suggest using a "surrogate key" - an Autonumber, a manually assigned number, or a programmatically generated one - as the primary key of the members table; the name should be stored *only* in the members table, and only a foreign key (Long Integer if you use an autonumber) in the payments table. [/QUOTE]