* Problem with Custom Text Scheme

[Tombaston]

I have a text scheme I created when I used FH4 that I use to help me identify areas to research. It uses flags to write BMD and 2 digit census years on the bottom line of individual boxes on a diagram. I can then easily see which items I am missing.

BMD flags 1.PNG (13.52 KiB) Viewed 4603 times

The code for the BMD part is
=ExistsText(%INDI._FLGS.__BIRTH_CERTIFI%,"B")=ExistsText(%INDI._FLGS.__MARRIAGE_CERT%,"M")=ExistsText(%INDI._FLGS.__DEATH_CERTIFI%,"D")

and for the censuses is
=ExistsText(%INDI._FLGS.__UK_CENSUS_184%,"41 ")=ExistsText(%INDI._FLGS.__UK_CENSUS_185%,"51 ")=ExistsText(%INDI._FLGS.__UK_CENSUS_186%,"61 ")=ExistsText(%INDI._FLGS.__UK_CENSUS_187%,"71 ")=ExistsText(%INDI._FLGS.__UK_CENSUS_188%,"81 ")=ExistsText(%INDI._FLGS.__UK_CENSUS_189%,"91 ")=ExistsText(%INDI._FLGS.__UK_CENSUS_190%,"01 ")=ExistsText(%INDI._FLGS.__UK_CENSUS_191%,"11 ")

Earlier this year I upgraded to FH6.2 and now when I apply the text scheme it adds backslashes before the % and =.

Looking at the item for the BMD flags it has become \=ExistsText(\%INDI._FLGS.__BIRTH_CERTIFI\%,"B")\=ExistsText(\%INDI._FLGS.__MARRIAGE_CERT\%,"M")\=ExistsText(\%INDI._FLGS.__DEATH_CERTIFI\%,"D") and similar changes have happened to the census item.

I can edit the items to remove the backslashes and it works fine again, but once I close and reopen FH or reapply the text scheme the backslashes come back.

Looking at the .fht file (attached) the backslashes are not in the scheme so it seems to happen when FH reads the scheme.

Any ideas, looks like a bug to me but I would like to know if anyone else gets the same before I raise it with Simon?

[Jane]

Where are you re-appying the text scheme from, are you simply selecting it from the list or copying it in from somewhere.

Text schemes in V6 are in Unicode and if you are copying in one from an earlier version of FH you may see some odd affects. Try cloning the text scheme to see if that fixes the problem.

[tatewise]

When you have edited the Template in Edit Text Scheme Item to remove the back-slashes do you use the Test button lower right to check it is valid?

I have played about with your Text Scheme and I suspect those Flags do not exist in some Projects in FH V6.

While in the Edit dialogue use the <<Insert button to open the Data Reference Assistant.
Under Individual - Flags are your Flags listed?

Those Flags must exist in every Project, otherwise as soon as you open a Project that does not use them, the Text Scheme gets upset in the way you describe.
Use Tools > Named Lists and Flags, select each Record Flag in turn, then click Flag Status and ensure that Always include this record flag... is ticked.

However, having said all that, perhaps a Text Scheme should not get so disrupted just because a Flag does not exist.
That should be reported to Calico Pie.

[Tombaston]

Thanks Jane and Mike.

I can't remember if I copied the fht file from my FH4 install into the Text Scheme custom folder for FH6 or if FH6 automatically imported it. I suspect the former as it had a problem with the census flags that were one character longer in FH4 and the text scheme complained about it. The BMD flags were fine.

So the text scheme in FH4 included =ExistsText(%INDI._FLGS.__UK_CENSUS_1901%,"01 ") for example, but when I went into Add Data Reference in FH6 it came across as =ExistsText(%INDI._FLGS.__UK_CENSUS_190%,"11 ").

As I have replaced all the census flag items I have effectively recreated it in FH6. Same issue with the FH6 version if I close FH and reopen it puts in the backslashes.

Yes I use Test and it says it's ok. If it's not ok it doesn't let you out.

The flags are ones I have created and I only have the one project so they are always there

I used insert in Add Data Reference to put them in and they are listed. As above I reinserted them from scratch when I first got the problem.

[tatewise]

On going through the process several items with different combinations of settings, it is entirely dependent on the Use Tools > Named Lists and Flags setting mentioned before.

If Always include this record flag... is NOT ticked then you get your problem for each such Flag, regardless of whether the Flag is used in the Project or not. So it seems that none of yours are ticked. That does sound worthwhile reporting to Calico Pie although you now have a workaround.

[Tombaston]

Thanks Mike that's fixed it.

I found the only one I had ticked was the 1911 one, which explains why that one didn't get the error. I have raised a support ticket with Calico Pie and will update it with what you found.