You might want to consider researching db normalization as I think you have repeating attribute fields. Member details are likely repeating fields where this attribute of a member should probably only be one field and the value should come from tblMemberStatus or whatever you'd call it. This might not be related to your current issue, but repeating fields often becomes an issue later on. One dangerous aspect is that you can end up with more than one field in a record with a value, which would usually be impossible under many circumstances (e.g. a member cannot be both current and inactive in practical terms, but can be because of the design). FWIW, I also advise against storing any calculations.
EDIT - for got to say that based on what I've said re: normalization, I also don't see the need for member details table if the records have a 1 to 1 relationship, which is what I think I'm seeing.
Last edited by Micron; 03-04-2021 at 10:58 AM.
Reason: chgd "active" to inactive
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.