There would be a simple solution but it won't be reliable if there is no way to associate family members, which is what I suspect by your post. That's because if there are 2 Smith families you have no way of differentiating them (unless you can do so by complete address or something). You could have a junction table just for this, or a field in that table whereby each family member gets the same association value. However, down the road you will have to manage this when little Johnny gets married and has his own family with the same last name. Then there is the fact that these days, not all women take the husband's last name, so a junction table will be more adaptive.
However, all that is moot if you've designed the tables like a spreadsheet, which your post suggests is the case. Seems like you have repeating fields:
Child1FN, Child1Birth, and so on.
and probably Child2 and Child3 and Child4... fields. That's a spreadsheet, and if that's what you have I suggest you research db normalization. You might get feedback on your current state if you post a pic of your table relationships, assuming you have created them.
Last edited by Micron; 09-17-2022 at 06:10 PM.
Reason: clarification
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.