Family Historian User Group

The 'safe' plugin script solution is to cater for every :match(...) operation possibly returning nil . Don't assume that such a match will always be successful, i.e. use defensive programming techniques. Similar techniques should be applied to all other operations to avoid unexpected failures. In th...

Yes, that is the same cause for the error.
The NSFX = POLLARD/ which is the trailing part of the NAME field and includes the slash /
So when the 'suffix' POLLARD/ is removed from Ella Loretta /POLLARD/ it leaves Ella Loretta / which does not contain two slashes and that causes the fault.

I discovered that fault arises under the following (unusual) conditions:
Name (INDI.NAME): Ian Steve /Munro/ Junior
Name Suffix (INDI.NAME.NSFX): Munro/ Junior
i.e. The Named Suffix field holds the trailing section of the Name field including a slash /

Yes, that is a good find from 2+ years ago!

Yes, I think that is the only manual method available and must be applied one Citation at a time.

To make a large number of changes in bulk will require a custom plugin to be written.

I think the following is the explanation but without seeing the diagram it is difficult to be certain. When cousins marry they bridge across generations so their relatives have two relationships to the other members of the family tree. The duplications illustrate where such people fit into their two...

You could create a copy of your master Project and delete the maternal line of ancestors.
Then the report will only include the paternal line.

The choice is yours. In Internet > Internet Data Matches... the Settings have the following options for both FMP and MH: 1) Enabled for all Projects except those with 3) selected 2) Disabled for all Projects 3) Disable for this project only The hints are only active for the people shown in the curre...

Yes, you must use Condition > Expressions instead of Condition > Record Flag
Use the << Insert Data Ref... button to add Individual > Flags one at a time, e.g. %INDI._FLGS.__LIVING%
Then the order of the Conditions determines the order of the icons.

That will refer to whatever happens to be the 1st Templated metafield in each Citation.

To refer to them by name see the Help for Understanding Data References and scroll down to Data References And Metafields as I explained earlier.

They had to be Templated Sources because Citation Detail and Reference are not Generic fields.
BTW: Once you create a Query it is immediately saved. You would have to specifically delete it.
You can use any existing Query to interrogate the Fields DRA without affecting the Query.

Unfortunately, the Query > Columns tab > Fields pane does not support Templated Named Metafields. Please refer to the Help for Understanding Data References and scroll down to Data References And Metafields . There it explains the data reference structure for metafields. e.g. %FACT.SOUR[1].~TX-REFER...

%FAMS.MARR[1].PLAC>STAN% is almost a perfectly correct Data Reference for the Standardized field. %CUR~FAMS>MARR.PLAC>STAN% is what you should use for the Marriage Standardized place. However, it is not allowed in the position you have used in a =FactText(...) function, so is ignored. The =FactText...

It might help if you could post screenshots of the Marriage Certificate and 1881 Census. See the FHUG Knowledge Base > Forum Usage under Attachments and Taking Screenshots for how to do that. Are you looking in Census records for a William about the right age with father John and mother Jane? Try th...

Welcome to the FHUG. It is quite common for entries on Census Returns to be erroneous and inconsistent. Unlike BMD Certificates that are completed near the date & place of the event, Census birth details rely on the person remembering and the enumerator hearing & recording the details correc...

Thank you for your reply but it does not answer either of my specific questions. If case sensitivity was an option and was enabled then: G%E%HAY% will NOT find Gordon Edward Hay or George Edmund Hays because HAY does not match. G%E%Hay% would work as long as the names did each start with upper-case ...

I'm not sure I fully understand how those wildcards work. In 21168|[Wish List 633] Name Filtering to handle inconsistent entry or miss slashing of names you say that the wildcard "%" covers any number of characters. Also, your examples suggest the filters are case-insensitive. So would G%E...

Plugin authors may no longer attach plugins to forum postings, so all old attachments have been deleted. Only a handful of users showed an interest in this plugin so did not seem worth publishing in the Plugin Store. If you have not deleted the plugin it should still be listed in Tools > Plugins... ...

Yes, it is not advisable to have various Projects in different locations. Why not? I have a live FH Projects folder for actual research projects, and a second FH Projects (Development) folder for test projects. It works very well, and I can easily flip between live and test projects using the Recen...

Yes, it is not advisable to have various Projects in different locations.
Ideally, all Projects should be in the File > Project Window... Location: path.

I presume in your examples that the Location: is just a drive letter.

What is it about paths under Parallels that are different from standard Windows paths? Some examples of paths you think are too long might help explain what needs changing. To ensure FH includes Media in backups requires the files to be within the Project folder. If the Project is called MyFamily th...

It is probably not the environment, just that FH hangs with the Not Responding message.

Use Unsourced Individuals link to download plugin V0.3 which adds a progress bar to prevent FH hanging.

An issue was discussed recently with regard to AS that has a SYSTEM.DATE option which is based on the PC locale format and may get mishandled when entered into FH source templates where the Short Date Format is different.
See Casting template data as a particular data-type (22911).

John, it is a bit more efficient to use the following to get day, month & year as integers. local dpDatePt = dtDate:GetDatePt1() local Day = dpDatePt:GetDay() local Month = dpDatePt:GetMonth() local Year = dpDatePt:GetYear() Once you have added the Date to a Fact it may be a good idea to use Get...

Mark, it was HKCU\SOFTWARE\Calico Pie\Family Historian\2.0\Preferences\ that I thought might need adjusting to match the PC locale date format read from the Windows Registry. Your suggestion of reminding the user of the expected short date format is probably better. John, yes, it is odd that SetValu...