Jacques Boucher is my husband’s half eleventh great-granduncle.
2 Likes
Boucher dit Derouche -OR- mine? Very surprising and CQQL, either way ~
Edit: I’m just now noticing both have the same lifespan. I was fixed on the Paigne surname.
1 Like
It is your Jacques Boucher, married to Francoise Paigne. This research was done by my daughter so I don’t know how accurate it maybe.
1 Like
I admit to not having spent much time on them, because I know there are a fair bit of avid researchers and relatives doing the hard work on those lines. Fun happenstance amongst the three of us.
1 Like
Hi, I like how you have your colors set to where it made this issue stand out for you. In my database, I only have 2 colors, 1 for my line and 1 for my husbands family line. I clear and set between us to ensure I don’t mess up each family line.
For my understanding, can you share/provide an example of the different criteria you set the colors. I may want to try some different settings.
Here in your example, without knowing how the colors were set, #29264 doesn’t look like he is related to his parents and #29260 is only related to her father. With having only 1 color set per person, you cannot see what other relationships a person is linked without clearing relationships and setting relationship by that person.
Well my colors are not really set within RM - I use Sqlite
The labels are as follows (see far below)
I used basically 2 scripts to color:
- I have a custom script that basically is based of the PersonTable and the Relate1, Relate2 and flags fields. I create a “temp table/view) there the logic runs of off.
I assign the colors in a logical order of my preferred logic order by “kinships”. (anyone where Relate1+Relate2 >0 basically is considered kinship. - For “non-kinships” such as inlaws of spouse by marriage and parent inlaw by marriage and similar. I did not change the label desc in RM Azure is actually not extended relationship, DNA match, nor kinship. These “extended” are detected with somewhat sophisticated logic and coded with order logic. Once a person is coded with a color the color is not replaced. Everyone color is reset when script is run. Azure is give to anyone remaining to indicate a stop point. Although sometime they are actually distant cousins that I have not yet plotted the path to common ancestor.
Yellow is my cousin so if a color pops up that is not expected that you know you have an additional relationship – this might be less obvious – but all people on left should be YELLOW unless someone has another path to home person.
Example here is George O Burbank would be yellow but he is also my Aunt 2nd husband which is why he is green
Another here
Green is expected on right but Louise Lavigne Married into a cousin of mine family so Orange would not be expected
This was because cousins/double cousins married in #30804 & 30813
#30796 & 30802 are 4th great Aunt & Uncle
@kevync1985 I completely understand what you are saying abt the problem and agree that it is wrong to show a cousin relationship over an ancestor’s relationship-- I have had a similar problem happen many times BUT in my case, it only show up in the aunts/uncles lines (g-aunt and g-uncles etc) – for example on my niece (actually all my nieces and nephews) --Dad and his brother married Mom and her sister-- so on my niece, my uncle shows up as a g-uncle BUT my aunt shows up as SPOUSE of the g-uncle instead of a g-aunt- So I am actually getting NON-BLOOD relationships over BLOOD relationships- I have figured out that this problem only shows up when you have either cousins marrying each other or siblings marrying siblings–and the SPOUSE of relationship always shows up on the Maternal side of the Maternal line ( or basically that the Paternal side of the Maternal line decides which relationship is listed as an ancestor and which is listed as the Spouse of..)–so I’m wondering if this is why yours shows 1st cousin 13 times removed instead of 13th g-grandfather..
Unfortunately your examples are too confusing for me – here is what I see:
Marie–same name on both–different numbers–one has parents listed–other has no parents listed–both have same dates for birth and death with one exact and one estimated-both have a daughter named Dame Jeanne LEMESTRE BOUCHER…
Jacques Jean Boucher and Jean Bouchard-- different numbers and different parents–again birth and death dates are the same with one exact and one estimated— the surnames could be variations of each other BUT the dit tells me they were from different places–again both have a daughter name Dame Jeanne LEMESTRE BOUCHER…
Dame Jeanne LEMESTRE BOUCHER–different numbers and different hubbies BUT the same exact dates of birth and death…
So to me it looks like Marie married her brother ( half brother) Jacque Jean Boucher BUT I keep telling myself that there MUST be something else going on here such as 2 Maries who are cousins and both had a dau named Dame Jeanne born in 1596 and ironically both died in 1671…
Yes you may get NON Blood over Blood if Spouse of (flag) in close than the blood relationship (in degrees of distance)
I do not usually view in descendant view but the colors will point that out above the RM description since only one is set. (The shortest path found)
Phebe children are expected to be all yellow but two are not
the life summary also show this
the family view show the people who married in who would be green unless they have another relationship (in this case they do so they are not green) #30796 & 30802
Both Sam #30802 & #30796 are siblings who married in
as for the question
”so I’m wondering if this is why yours shows 1st cousin 13 times removed instead of 13th g-grandfather..”
maybe BUT – other software calculates its the same way- so its NOT just RM