If this is considered reasonable behavior, then why does the flag table define Flags=2 as “Spouse of male blood relation ie display uses Father, Uncle, Cousin” and Flags=6 as “Spouse of female blood relation ie display uses Mother, Aunt, Cousin”? And if this is by design then it is a very bad design because it would indicate that if the spouse of an uncle/aunt remarries and has issue from that marriage those children from that marriage will be blood relatives.
I don’t have a case to test, but I don’t believe this actually happens.
I went looking for the post that I thought Renee made but didn’t find it. However I did stumble on a link where people were discussing an enhancement for relationships where they discuss the spouse of an Uncle/Aunt being an Aunt/Uncle and this has been a long time feature in RM. That thread is at Set Relationship - Enchancement request
The spouse of Aunt or Grand Aunt or Great Aunt (of Uncles) should not matter as far as flags go. Either they are blood or spouse of. I would have to change POV in my DB because I am also blood related to my only aunt by marriage.
My response wasn’t to you. I really fail to see what your issue is as i haven’t read it that closely. I responded to Christine who seems puzzled that the spouse of an aunt is shown as uncle…which is correct and reasonable to expect as it is true.
The I pointed out is not related to what Christine has an issue with – that issue should be long in own thread.
THe issue I point out is that when a person is no longer related (could be path changed or “home” person for relationships was changed — there will be times when a non related person flags are set to non zero which would be wrong as releate1 & relate2 both zero - I used one of my more distant cousins to demo that – they were 6 people related to him but not to me that despite using CLEAR in RM – it did not clear flags. Only clear relate1 & relate2. Left Flags sets to “spouse of”. that is sloppy code if intentional. I will say – that it might not impact RM relationship calculator etc but we really do not know and it makes me uncomfortable what other coding issue(s) there might be.
Thank you Kenneth. This is a helpful request. I am able to toggle this myself via SQLite but I think a toggle at the software level is helpful. I am a forensic genealogist and work on probate and guardianship cases so differentiating between a spouse and blood relative is crucial for my business. Having to go through and manually change this for the spouse of each aunt/uncle or niece/nephew is just one more step that I would like to see automated.
@Christine_Cochran
– please tell us what version of RM you are using-- RM 7, RM 8, RM 9 or RM 10 as the results are different in some of these versions…
1 Like
actually even with 10.0.0 to 10.0.3 have different results.
I am using RM10.0.3.0 on Windows 11 the latest update being 2025-01 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5050009)
S
Correct you should have different results
There were 2 other discussions going on at the same time as this one
Set Relationship - Enchancement request --all abt issues that were going on with set relationship and RM fixed it in the next update BUT can’t tell you which update…
there are still issues with 10.0.3. First not clearing flags.
2nd many users have reported with inconsistencies ( maybe relate to flags not being cleared)
Kevin