I've been reading through several posts about similar topics, but I'm just missing something here. I imagine some of this is due to some problematic base design, as I've been building it as we go but here's where I'm at -
I have a table of club members. We are in the yearly renewal time, so, since I didn't have a way to allow submissions from our membership form to update existing records, I have redirected submissions to a new table. As it is possible folks have different emails, phones, etc, and they aren't aware of the formulated member ID I've assigned them in our main table, this seemed the easiest way to collect new and updated form submissions.
So, my plan was to do a comparison between are All Members table and the 2024 Membership table -
1. In All Members table, If email exists in 2024 Membership table, update a field to indicate member has renewed
2. In All Members table, if a record in 2024 Membership has the same email, compare other fields for any updates
3. If a record comes into 2024 Membership and the email is not the same, flag it to be reviewed as a potential new member or a returning member with a different email
I'm already using a number of lookups to additional tables to track things like:
Committee Memberships
Payments Received
Precinct Location
But trying to create the first simply look up that would just create a Y/N field in All Members if the email in that record matched a record in the 2024 Membership table is eluding me.
Any guidance is appreciated 🙂