Hi Sally, thanks for getting involved.

Record Count V06-12 gives the same result at the Summary Info (22090).

It does not seem to matter which of the two menu options Count of records entered within <date range> V07-12 is being run from:
System Reports\Statistics
Statistics
In fact the XML looks to be identical apart from the MenuPath.

It makes sense for a date range query to exclude unknown dates.  Guided by the XML I checked Survey_Event.Vague_Date_Type and did not find any with 'U'.  I was looking in an exported Access database as that is the only way I have to see things at a table level.  A handful of records were excluded from the export for validation errors, but not on the scale being seen in the total figures and no mention of things being excluded for unknown dates.  Taxon_Occurence has 22084 records, which seems reasonable if you take into account the validation errors.

RecordStats claims to be counting records by year added, a bit misleading?

Is it worth seeing if other people are getting strange results (surely the issue would have come up by now?)

Maybe I should send the export file to you?

Thanks Charlie.  Looks to be my data then.

I have taken a look at the export file you sent me and have found that the Entered_By field on a lot of taxon occurrences contains a name key that isn’t in the Name table or the Individual table. The same applies to survey events. Count of records entered within <date range> V07-12 only includes taxon occurrences when the Entered_By on the survey event has a corresponding entry in the Individual table so this is the reason for it returning such a low count. The Recorder 6 user interface should not allow these problems to arise but they could have happened as a result of system crashes, power cuts, bugs in earlier versions of the system or changes done incorrectly by users with Microsoft Access or SQL Server in the database itself. As the problem names are from other systems you may be able to rectify things by reimporting them, assuming they aren’t missing in those systems. This can be done by creating a rucksack containing the names, opening it and using Tools – Export Data to do an export. With a rucksack open it will export the things in the rucksack and give you the option of whether to include the associated observations.

Anyone facing issues like these would be well advised to use the package called Problems V2.zip to check for various problems. It can be downloaded from http://forums.nbn.org.uk/viewforum.php?id=33&p=5 . It contains a number of xml reports and batch updates designed to detect and correct problems in Recorder 6 databases. The documentation in it has been written to help users with correcting the problems found. Running System Reports – Information – Sy06 - Problems(Summary) via Reports – Run will provide a summary of the problems. This often reports thousands of problems many of which can be corrected by batch updates. Running the batch update DATA_Correction 1 will correct several types of errors very quickly. If the reports and batch updates aren’t already in your system the documentation in Problems V2.zip explains how to install them.