How to Remove The 'Set Preferred' of No Spouse
One of my female ancestor records (Jean) shows up with Preferred Spouse ticked, date of marriage etc and six children, then below that is the same Jean, with the same reference number but showing her as being with no spouse and five of the six children listed (again identical references as above).
When I click on Set Preferred, it shows two options
John D.. (correct husband)
No Spouse
The first option has been selected, but there remains this anomaly of her name appearing twice and I can't see any way to remove it.
How do I remove the 'No Spouse' option to stop it showing all this excess unnecessary duplicate information as if she has had 2 spouses?
All the children are born after their marriage, there was no period where she had 'No Spouse'.
Best Answer
-
@Venetia74 I see this often. I still haven't figured out as why this happens, but the solution is simpel. The child is connected twice to the mother (or father). To solve this, go the child where the child has only one (!) parent. Then click the pencil behind the child and remove the entry for the parent. Refresh the screen. You should see now that the child is showing only with a entry for both parents. Repeat this for every other child where you see this happen.
1
Answers
-
Thank you so much, I will try that.
0 -
Done, thanks again.
1 -
This situation often arises if two duplicate fathers or mothers are merged. Suppose one of the parents has their spouse and the children as a simple family, and the other has only those children (identical PIDs) and no spouse. During the merge, there will be the option to move the children from the left side to the right. Depending on which of the duplicates is chosen as the survivor, the spouse may be on the left side and also be able to be moved from the left to the right.
In the scenario that you have described, it is likely that the mother Jean was on the left side with the children and no spouse. In that case, the merge would default to moving them all to the right side. If the merge continued like that, the result would be as you have described. It would have been possible to avoid this result by undoing the default by moving the mother and children back to the left side before proceeding to the "Reason" stage. Before moving them back, you would need to check that the each of the corresponding children in the two relationships are in fact for the same PIDs and not duplicate children.
0