Helping Family Historian users since 2002
https://fhug.org.uk/forum/
. Doubt that there’s a single FHUG contributor on the rising side of the curve...ColeValleyGirl wrote: ↑27 Dec 2022 16:44P.S. Your definition of youngsters is a bit imprecise... How young do you think we all are?
Hopefully you never grow up! More fun that way.Robert Jacobs wrote: ↑28 Dec 2022 01:38I'll be 84 next month and I keep wondering when I'm going to grow up.
Answered in the first response to you.
In brief, for FH, full GEDCOM compliance is a major design goal (hence the two categories), but there are ways to achieve what you want within that constraint.tatewise wrote: ↑21 Dec 2022 10:56FH closely follows the GEDCOM specification and by doing so makes migration to and from other products fairly easy.
The more FH strays from the specification the more difficult such migration becomes.
Many other products distinguish between Events and Attributes as defined in GEDCOM.
In practice, there is little to stop you from using an Attribute as both an Event and an Attribute, except that the narrative Sentence Template definition may be a challenge to cope with both scenarios.
You could also define both a custom Event and a custom Attribute with the same or similar name. FH warns against it but it is allowed and fully supported.
There are several extra standard GEDCOM fields available for facts but they are not shown on the Facts tab so the All tab must be used. Adding custom fields would jeopardise migration to other products.
The recommended approach is to add labelled text to the Note field as explained in the FHUG Knowledge Base article Narrative Report Fact Sentence Templates under Custom Fact Fields.
)