Census Date Check query

davidm_uk · Post by **davidm_uk** » 26 Apr 2010 19:42

Having now tidied up all my census flag tags and descriptions, and resolved quite a few census flag check errors I'm now just left with two Census Date Check 'errors' that I don't quite understand, or be able to get rid of.

I've tried using the reallocate function for each of the two entries, but that doesn't clear the them. Maybe there's still some anomaly left in GED file from where I had manually changed the census tags?

Anyone any ideas?

It doesn't seem to be affecting the operation of FH or AS, I just wanted to tidy things up!

ID:4528

davidm_uk · Post by **davidm_uk** » 26 Apr 2010 20:03

Ah - managed to clear the 1901 entry, found that I had an old (manually entered) census event with no place recorded.

I've now run the same query (listing all individuals having a census event for 1891, and showing the place name), but the place names all seem to be ok, no blanks or funny characters in there.

Post by **nsw** » 26 Apr 2010 21:25

I don't have a lot of experience of FH queries but how about if you create a query where you have the columns:
Individual: %INDI%
Census: %INDI.CENS[year=1891]%

And for the rows add:

Condition: Add If
Expression: %INDI.CENS[year=1891]%
Operator: matches
Value: (leave blank)

davidm_uk · Post by **davidm_uk** » 27 Apr 2010 15:00

Hi Nick,

Thanks for the suggestion. I'm somewhat of a novice on on FH queries, so not sure what your query is trying to show but the select row expression

Condition: Add If
Expression: %INDI.CENS[year=1891]%
Operator: matches
Value: (leave blank)

doesn't return any individuals.

However

Condition: Add If
Expression: %INDI.CENS[1].DATE:YEAR%
Operator: equals
Value: 1891

with colums
%INDI%
%INDI.CENS[1].DATE:YEAR%
%INDI.CENS[1].DATE%
%INDI.CENS[1].PLAC%

lists all individuals with a census entry for 1891, and the dates displayed are all correct (5 April 1891), plus the place names all seem valid.

If you could tell me what your census date check is actually testing for I might be able to produce an equivalent FH query, or even open the GED file with a text editor and search for that particular error.

David.

Post by **nsw** » 27 Apr 2010 15:11

If the query isn't returning anything then that's a bit odd - it is looking to see where a place is blank and the census year is 1891. [EDIT: No it isn't - please see my next post below] This is what the Census Date check is reporting.

I think the problem with your query is you are only showing individual with 1891 census as their first census. So you would need to also look for:

%INDI.CENS[2].DATE:YEAR%

and add the columns for that too (and [3], [4], [5], [6], [7], etc.) I believe the use of the [year=1891] means it will detect any census fact with year as 1891 and this was a special feature by Calico to help with census queries. Actually I wonder what it would do with my query if an individual had two 1891 census events and the second had a blank place? Perhaps Jane or someone else equally adept at query writing could help.

Alternatively, if you would be happy to email your file to me (there's a link in the A.S. help menu) I'd be happy to find the problem for you. Naturally I wouldn't look at the genealogy data in your file and wouldn't pass on to anyone else.

Cheers

Nick

Post by **nsw** » 27 Apr 2010 15:21

Sorry I can see the mistake in my query. I've missed the Place off it. I think it should be:

Condition: Add If
Expression: %INDI.CENS[year=1891].PLAC%
Operator: matches
Value: (leave blank)

PeterR · Post by **PeterR** » 27 Apr 2010 16:06

If you have FH v4, you can also use a Fact query, e.g.:

Note that the above filters catch both possibilities: (a) that there is no Place field, and (b) that the Place field is empty.

davidm_uk · Post by **davidm_uk** » 27 Apr 2010 16:25

Hi Nick,

Before seeing your last two messages I'd concocted a query which did find a census event with no place name (or source). I think it arose from an abortive attempt (a couple of years ago!) to merge a GED file that someone sent me. I've deleted the event (added a note to the individual as to where it came from) and that has cleared the final error report in AS.

Out of interest (maybe) the query I ran was:

Rows
Add If: =IsEvent(%FACT%)
Operator: is true

Columns
%FACT.DATE:COMPACT%
=FactLabel(%FACT%)
=FactOwner(%FACT%,1,MALES_FIRST)
%FACT.PLAC%

It also threw up what at first I thought were some duplicates, but turned out to be father and son with same name living at same address!

Many thanks for your help.
David

(a contribution towards your development fund is on it's way).

Post by **nsw** » 27 Apr 2010 18:58

PeterR said:
If you have FH v4, you can also use a Fact query...

Thanks Peter, I knew there was a better way. Presumably the 1891 could be a prompt so it could be used by anyone who has a similar problem in the future to deal with any other similar issues spotted by A.S. in the future?

David: I'm pleased you found the rogue placename and thanks for your contribution to the A.S. project.

Best wishes

Nick

Family Historian User Group