Family Historian User Group

Why are you using the tostring(...) function? That will sort alphanumerically as text, i.e. "1", "11", "12", "13", etc, will sort before "2", "21", "22", "23", etc. Since the values are all numbers just use a.GEN < b.GEN...

Welcome to your first FHUG posting. See the FHUG Knowledge Base > Recording Children with Foster/Adoptive Parents and How to Handle People With Multiple Names . The usual convention is to enter the Birth Name as the Primary Name and Adoptive Name as an Alternate Name. But the reverse is not unreason...

To be honest, although we have found a workaround, I don't think the surrounding chevrons should be necessary.
Try reporting the original symptoms to CP and see what they say.

I admit that is a bit strange and rings a small bell at the back of my mind thast it has happened before. Anyway, those spacing issues are associated with the top level item handling that automatically should put a space after each symbol such as dor (.) and comma (,). The solution that works for me...

You are correct Steve. There is no such expression that is infallible. The worse situtaion to cope with is where a distant relative on your father's side married a distant relative on your mother's side, in which case everyone is on both sides! Think about it. It is easy using the IsAncestor(...) fu...

Dear Tatewise, Your reply perfectly illustrates the issues raised by a standard which cannot be followed by developers due to basic weaknesses. I'm not sure whether you mean the weaknesses are in the GEDCOM standard or in the developers! :lol: In my experience of writing my Export Gedcom File plugi...

Welcome to the FHUG. IMO you have misunderstood the ASSO tag definition in GEDCOM 7.0. It does allow the ASSO tag to be applied to facts as well as individuals. See Page 38 where the ASSO tag is shown subordinate to the BAPM event to associate @I2@ as the clergyman: 0 @I1@ INDI 1 ASSO @VOID@ 2 PHRAS...

To prevent magic characters having their gsub(...) magic effect they must be prefixed with an escape % character. Prior to UTF-8 the code "(%W)" could be used but now that may not work if the sting has UTF-8 symbols/accents. So now the code "([%^%$%(%)%%%.%[%]%*%+%-%?])" must be ...

What you describe means that I have to re-enter all the data into the new template, even though only the name has changed. Is there no way to split off certain sources under a new template name? No you don't have to re-enter all the data held in the Source record. As long as the metafields have not...

I'm not sure what you're doing to change "instance of the old template" because templates don't have instances. You must use Tools > Source Template Definitions... and then Clone... the original definition but give the clone a new Template Name probably including the name of the country. F...

You'll need to explain exactly what you are tailoring in the templates to suit each country. Presumably, you expect to end up with as many templates as countries? The complications involve adding/removing metafields. If a Source record uses a metafield in the orginal template that gets removed from ...

Hi Margaret, there is a common misconception regarding Individual Record Flags and Diagram Icons. They are two quite independant features of FH. See FHUG KB > Using Icons . Setting a Record Flag does NOT automatically cause a Diagram Icon to apppear under the Individual's Box. Also, many different t...

Thank you for giving it a run, but odd that it failed on copying the files, since that always worked, and it was the Windows Registry export that was under investigation. There is no hurry to debug.

It has taken a while for me to get around to updating my legacy plugin for the latest Linux/WINE features. However, the plugin Backup and Restore Family Historian Settings - V3-6+1 is available via the link below. It now inhibits being run in standalone GEDCOM mode and uses exactly the same script f...

The colon is nothing to do with the RootsMagic Import (project) Fact Set. It indicates that the fact is a custom Attribute ( not an Event ) and expects a value after the colon, which can be entered in the box to the right of the label Second Boer War: in the pane below the Facts list. When you creat...

To amend Marriage details you need to open the Family record Property box. Do that on the Focus Window by clicking the blue Marriage bar that runs across under the spouse boxes. Then on the Facts tab shown in the Family record on the right the Marriage Events are listed. Use the large red X to delet...

I advise that you update otherwise every time you run the Ancestral Sources Data Entry plugin from FH you will get that same popup memo message.

The later version fixes some issues, explains the difference between the AS program and the plugin, and lets you choose the Individual to start AS with.

Simply append the expression to the existing caption expression, enclosed in the square brackets if you wish. e.g. %INDI% [=Relationship(FileRoot(),,TEXT,1) =TextIf( IsInList(,"Fathers Side"), "Fathers Side", TextIf( IsInList(,"Mothers Side"), "Mothers Side", ...

Welcome to the FHUG. On the assumption that the data in the Ancestry Family Trees has been updated over the intervening 3 years, then yes download the updated GEDCOM and delete the old Projects. That assumes that you have not significantly 'tidied' the original downloaded Projects as advised in the ...

OR in the Focus Window select the blue bar often displaying Marriage details below the partner's boxes. OR when you select Charts change Tree Root Type to Couple and select the Root Couple. image.png Those options are all explained in FHUG Knowledge Base > View Both Spouses’ Ancestors in Diagrams th...

There are several issues there. Firstly, why bother with Record Flags that you must manage to keep synced with the Census facts? Use the Census facts themselves as the 'flag' to create the green tick entries. i.e. Instead of =Exists(%INDI._FLGS.__CEN_18417%) use =Exists(GetFact(%INDI%,"EVEN-BRI...

You appear to have discovered a fault in the FH Media Report. FH V7 changed from GEDCOM v5.5 format to GEDCOM v5.5.1 format which alters the Media record structure. The Title, Format & File data references are different but the Media Report still uses the old data references. Therefore, in the M...

The only way to bulk populate the Fact from a Named List would be to write a custom Plugin. So why not use the Named Lists directly and keep them popluated with the appropriate Individuals? Then in the Caption at the top of the Property Box identify whether Fathers or Mothers side. Use Tools > Prefe...

If so, how does one set it when not using A.S.? You can set it in the Citation Window/Source Record dialogue: If it is a Generic Source, then the Generic Type field is displayed by default. If it is a Templated Source, then the Generic Type field is managed on the Source Record, Property Box, All t...

Ancestral Sources Data Entry plugin Version 5.1 Date 07 Oct 2024 is published in the Plugin Store and fixes the Standalone GEDCOM issues.