* DEAT record

[ronk]

My Gedcom has some DEAT Y/N records, originally exported from Legacy, which were set as specified by the tick of 'living, yes or no'. Occasionally an error is made as in this example. This is for people without a death date and the Legacy default there was not living. Where in FH does this flag appear? I didn't notice it was 'Y' until after export to TNG that this living individual was displaying even when not logged on, though living should be private only.

Update:I may have found it in FH; is take the form of a 'fact' in the property box facts tab, such as:
------ died ? This individual has such a fact. If so, never mind. Will delete the fact, and the DEAT should be deleted, right?

[tatewise]

Those Legacy 'facts' look non-standard.
Yes, delete the FH Fact to remove it completely.
If you use the All Facts Query you should be able to sort them together and delete them en-bloc.
FYI: FH has a Living Flag that is often used in Privacy setings.

[ronk]

I may have some misconceptions, but I'm not sure I wish to delete all of these; most are legitimate and determine whether visible as non-private per my TNG settings. I think w/o that record TNG (and Legacy, which I back-fill from FH) would assume living, i.e., individuals w/o a death date but who are deceased. I checked my FH gedcom and found ~1900 '1 DEAT Y' records.

I didn't think it was non-standard, since if you add a DEATH fact, it appears the same as the incorrect fact I deleted:

1.jpg (1.73 KiB) Viewed 3496 times

However, checking the gedcom, adding the DEATH fact created just a DEAT record w/o the 'Y'.

BTW, is the All Facts Query a plugin or an FH Query? Where is the FH Living flag?

[tatewise]

Sorry Ron, I misunderstood. I thought the Legacy living, yes or no option produced a non-standard Fact separate from the standard DEAT fact tag.

Here are the rules.
Usually a DEAT tag, like any other Event, is not allowed anything on the same Gedcom line.
But if it has no DATE tag and no PLAC tag it should be followed by Y on the same line to prevent such otherwise blank Events from being discarded.
Such blank Events cannot be followed by N on the same line.

You have discovered a small anomaly in FH that I reported to Calico Pie a while ago, regarding new blank DEAT and other Events.
When initially created they have blank DATE and PLAC fields internally, so the Y is not required.
But when first saved, the blank DATE and PLAC tags are automatically removed, and the Y is still missing.
BUT if you open and close FH for that Project it rectifies that mistake.

See View > Standard Queries > All Facts and also All Events.

See Help > Search Help > "Record Flags" (with the string quotes) and review the topics with Record Flags in their title.
They are covered in the FH Book Getting the Most From Family Historian that I hope you have studied intensely

[ronk]

But when first saved, the blank DATE and PLAC tags are automatically removed, and the Y is still missing.
BUT if you open and close FH for that Project it rectifies that mistake.

I did verify the gedcom DEAT line anomaly you reported ...the 'Y' is missing initially, then added after an open/close.

Thanks, and yes, I need to read more of GTMFFH5 guide. Based on comments from early recipients of the new GTMFFH6 book, and the Amazon price of $23.95, it looks like I will be sticking with the V5 pdf version for now.