New user create 2 table membership database
I want to build a membership database with two tables. The "parent" table will be "Members" and contain contact fields. The "child" will be a "Dues" table for annual payments. I assume that this is a pretty common and basic relationship, but I'm not clear on the "Primary Key field" logic. If I use a numeric auto-create primary key on "Members", do I also create the same for "Dues". Are there any examples or tutorials covering this?
I am reading the "Missing Manual", but the relationship structure is still confusing.