Page 1 of 1

Showing people as Never Married in Custom Query

Posted: 03 May 2022 10:49
by Little.auk
Hi
I have a custom query that has a column that displays Year Married - I want to modify the expression to display "Unm" for people I have confirmed never married -- to differentiate them from those people for whom I have not yet found / recorded a marriage.

The Property Box displays a "Status" box for recording the relationship status, but this is a "Family" field so requires a "Spouse" relationship to be recorded, but the people I am looking at had no "Spouse".

I think I will have to use a "Never Married" Custom Flag and a TextIf expression to do this, but is there any other way of recording that someone "Never Married" when there is no "Spouse"?

Re: Showing people as Never Married in Custom Query

Posted: 03 May 2022 10:56
by LornaCraig
There is a standard Individual fact called Marriage Count which you could add to the individual and set to zero.

Re: Showing people as Never Married in Custom Query

Posted: 03 May 2022 11:08
by tatewise
Then in the Query Column, you could use TextIf that Marriage Count = 0 and display "Unm".

As a matter of interest, how does you Query cope with people who have married more than once, or have had an initial 'relationship' with 'illegitimate' children (Spouse tab 1) and later get married (Spouse tab 2)?

Re: Showing people as Never Married in Custom Query

Posted: 03 May 2022 12:28
by Little.auk
Hi Mike,

I found, by trial and error, that FH ranks Spouses based on their tab positions in the Property Box - from left to right (or top to bottom!) regardless of their chronological sequence.

By ensuring all my 'Direct Line" spouses are the left hand (Top) 'Tab 1' they all become SPOUSE[1], thus making Direct Line queries straightforward.

For relationships resulting in illegitimate children I use the "Status" field in the 'Spouse' tab of the Property Box and set the relationship as 'Never Married', or 'Unknown', however, I don't think this matters, as there are no marriage events for these relationships. I only have a couple of instances where the father is recorded.

Re: Showing people as Never Married in Custom Query

Posted: 03 May 2022 12:58
by tatewise
Yes, you can adjust the instance order of most items in FH. Just beware of using any of the automatic chronological sorting commands such as Tools > Re-order Out-of-Sequence Data..., etc. There may also be consequences in Diagrams and Reports where details will not be chronological regarding marriages & partnerships.

So I assume that your custom Query is only interested in your 'direct line', lefthand, 1st Spouse tab entry.
In that case, it seems unlikely such Spouse tab entries would be confirmed as unmarried bachelors/spinsters without children, because how could they then be direct line ancestors?
However, if needed, the Marriage Count 0 attribute seems like the best solution.

Re: Showing people as Never Married in Custom Query

Posted: 03 May 2022 15:30
by Little.auk
Several reasons, but the basic one is that I have people in my tree who, although records say they were married, I have not yet found a marriage record.

One of the purposes of this particular query is to highlight those. So flagging people I definitely know were never married eliminates them from the "No Marriage Information" list.

Where did I say unmarried without children?

I have several cases of illegitimate children - my 2x G Grandfather William was illegitimate and his mother, my 3x G Grandmother, Hannah, never married, she died, a spinster in 1875. So although she had at least two (illegitimate) children, there is no point searching for marriage records as both the 1871 census and her death certificate in 1875 say she was unmarried.

However, I know who William's father was, he was also illegitimate! In his will he left both William and Hannah significant bequests. From the will I also found that he fathered at least one other illegitimate child, William's half sister, Rhoda, also a beneficiary.

At 76 my memory is still not bad, but it is not as good as it was. I am finding I need to keep much better records and plans to keep my research on track, and particularly to try not to plough the same furrow twice (or even more!)