* Publishing Descendant Text File Locks FH

[waveydavey2016]

Hi all,

I think I have just come across a bug in FH 7.0.20: A tiny minority of the people on my tree were born and then died immediately after birth. In this case I have given them the name <Unnamed> Adams or <Unnamed> Warren as I feel that the deserve to be noted. But if I then ask to publish a descendant text report which contains these names, then FH locks up and has to be killed. This is shocking for me - it just doesn't normally happen! Could anyone either put me straight and tell me what characters I should be using or alternatively do you agree this is a bug in the software?

[tatewise]

Can you be clearer about what kind of report you are producing.
Is it a Narrative > Descendants by Generation or an Outline > Descendant Outline report?

Are you saying that if those people with <Unnamed> as their first name are not included then the report is produced OK?
What happens if you change their first name temporarily to something else or perhaps nothing at all?
So their names are just Adams or Warren.

[RS3100]

What happens if you remove the brackets? I have several people referenced with "unnamed" or "unknown" in their names, such as "unnamed male infant MERRYWEATHER" or "unknown GILPIN" (i.e. unnamed male infant /Merryweather/, unknown /Gilpin/) and have no such issues with narrative reports.

I have been regenerating numerous narrative reports to proof read them (again) due to CP keep fiddling with the {note} and {inline-note} functions, and have not had any such problems.

[waveydavey2016]

Sorry for the delay: The report I am requesting is: Narrative Reports > Descendants by Generation.

I have tried removing the < and > from the name and this fixes the problem. I hope you don't think I am being picky, but these symbols haven't caused previous versions of FH a problem. I'm happy to remove the greater and less than symbols, but I was just trying to denote that the name of the person wasn't "Unknown" - however unlikely that confusion would be!

[tatewise]

Those < and > symbols should not cause FH to lock up when producing any Reports.
However, I have added a forename <Unnamed> and the Descendants by Generation report is OK.
So your symptoms must be caused by some other side effect of adding those symbols.

My guess is that somehow a Sentence Template which uses < and > symbols in its syntax is getting confused by those symbols in the person's name. So your challenge is to discover how that is happening. Do you have any customised Sentence Templates, especially for the facts that those <Unnamed> Individuals have recorded?

Then the problem can be reported to CP with a greater chance of it being fixed quickly.

[waveydavey2016]

Hi Mike,

I have tried a number of things. Removing the < > in all cases allows the production of a Narrative Reports > Descendants by Generation. The data in this database has come from a number of previous family tree programs so I wondered if these symbols were old character codes which FH didn't like? I added the < > symbols to a number of the people who had this previously and FH works fine.

But: I had an <Unknown> Adams which still locks up FH. I renamed this person <Female> Adams and FH still locks up. I deleted this child and re-added as <Female> Adams but this still locks FH up! (there is literally just a Quarter of year birth and Quarter of year Death and the GRO references). I changed the name to "Female" Adams which works fine.

So for this time being I have changed the name to Female Adams which obviously works fine.

[tatewise]

It would be really helpful if you can create a copy of your Project with the < and > problem so that it can be investigated further and perhaps sent to CP for investigation of the cause.
If that copy Project can be pruned down by removing records but still exhibit the problem then all the better.

Does it matter which Individual is the Starting Person for the Narrative Report?

[Fairperson]

I am running FH 7.0.20 on a Windows 10 PC

I recently experienced a problem where FH would “hang”, requiring the FH process to be terminated as the only way out. This only happened on certain individuals. The “Individual Summary Report” would work OK, but the “Individual Narrative” Report would hang the FH application.

Investigation revealed that in one of my “home made” FACTS attached to the individual I had typed in the FACT sentence <age> instead of <{age}>. I could replicate this effect by modifying the FACT sentence.

Whilst I am pretty sure 7.0.19 tolerated this mistake by me, 7.0.20 does not seem to!

Do you believe this to be a similar problem, possibly introduced by 7.0.20?

Hope this helps

David

[tatewise]

Thank you David, that sounds like it may be an associated problem.

If you have not reported that problem to CP then please do so ASAP via http://www.calico-pie.com/osticket/open.php

[Fairperson]

Thanks Mike,

Ticket #262326 logged with CP. Lets see what happens!

regards, David

[Fairperson]

G'day all,

Just to let the group know that CP can replicate the condition and advise that it will be addressed in the next update.

David