FTAnalyzer questions.

Are you sure that you have identified the reason for the error and not just found a coincidence? I don't get FTA errors in such circumstances.

FTA does have an error in the identified line of your report. Some/all of the count given can actually refer to instances where there are census facts recorded without corresponding LC facts. Both counts are added in together.

 

Yes, I am certain that when I have
Event: Census
Date: 1881
and
Event: Residence
Date: 1881
that I get that error

Here's why
Currently I have no errors in that spot


I'll find a random person who I have entered on LC for a census and duplicate their census entry and make it a Residence instead - thus giving them both a Census and a Residence fact for the same year.

And Bingo, I have an error

 

The only way I don't get that error there is to Untick the "Treat Residence as Census Fact" which I'd like to keep ticked if possible but if that's the only way to avoid the issue then so be it

 

I think that Alexander will suggest that you untick the "Treat Residence as Census Fact" just like he did to me several months ago, possibly in this same conversation. He explained that this equivalence option was only put in place for use when census facts could not be adequately entered. You do not need it and that is what is causing you problems. Just one 'duplicated' record changes many of the error counts considerably.

You might be able to keep it ticked as long as there are no duplicated/overlapping dates for the Residence and Census records but why would you need to go to a lot of extra effort unnecessarily?

 

Now that I've managed to resolve the 60 something errors I originally had in that spot, I probably will leave it unticked so that I can have a residence and a census in the same year - specifically for events like baptisms, marriages and burials.
And especially because often time where my folks are living, the only semblance of an address given on the census form is the town or village, not even a street to go by.
But it's taken this whole conversation to work out that what I was asking for was already there anyway.

 

Can do, and will do - how would you like to receive said Gedcom?

 

I had residences thanks to the Ancestry-FamilyTreeMaker issue - I've since been able to largely remove the pertinent census year problems, and am working on the other residence/census facts to get them all to census

 

V5.0.1.4 recognises census references from Notes but there still seem to be some problems with 'Lost Cousins' and 'Colour Reports' tabs.
Should references found in Notes be used in all reports?
Some notes are being ignored and what works for 1841 (yellow tile) does not work for 1881 or 1911 (orange tiles)!!
It is late so I don't have time to give full details now but will raise an issue, with Gedcom, in the morning unless you notify that problem has been corrected.

 

Issue 13555 now raised and mini Gedcom file attached with data to illustrate concerns/questions, using v5.0.1.5 of FTA.

 

Is there some way of telling FTAnalyser who the root person should be if it picks the wrong person (for some reason?)

 

It would appear on the surface that it does indeed work.
Will have to look at it in detail in a week or so, have a death in the family to deal with right now.
Please nudge me for a reminder if you've not heard back from me by mid-May in regards to the shared facts.

 

I was investigating a problem in one of my trees using v5.0.2.0 when I was informed of a new level, v5.0.2.1, which I downloaded.
That seemed to cause more problems so I raised issue 13570.
Now I notice that there is a further bug fix level, v5.0.2.2, available. However, the list of updates and bugs fixed goes back several minor levels.
Please can you indicate what the changes are for each release so that users who try to keep up to date can easily identify whether the changes may be relevant?