I'm in the process of developing a membership database wherein a Membership# is given to either a single person, or shared by a couple. I am wondering if it is possible for each record in a single form to inform up to two records in a table. i.e. filling in a single form will record values in two consecutive table records.
I realize it is probably poor practice to start with a form and work towards linking it with table data (instead of the other way around). In any case, I feel like my only other option would be to create separate "1st Member" and "2nd Member" tables to link to the form, but since each table would contain the same fields, I don't see this as the best way to go.
I feel like the root of my problem deals with starting with properly normalized tables; when conceptualizing the database, I struggled with how I would organize the data. My main issue is that the Membership# is not necessarily unique between two people, since they may be a couple. And yet I need to be able to treat couples both as a SINGLE UNIT (sharing mailing address, phone number etc.) and as SEPARATE entities (with unique attributes like birthdays and names), while keeping in mind that not all members are couples.