There is an issue in the reports in that the dates they're reporting are limited in value by SQL standard behaviour to between 1753-01-01 and 9999-12-31.   Rather than changing all your data I'd suggest the reports be modified to cope properly with historic dates.  I'll recommend this.  In the meantime I've emailed you a version of the CountSurveyRecords report which copes with all dates plus it also returns organisations and not just individuals.  The ProblemDeterminationDates would require a bit more tweaking to get it working for older dates.

Thanks,
Simon

Yes, quite right. All our surveys were set to allow records from 1650, and changing them to 1700 didn't help. The Count of Records made within Date Range report doesn't allow dates before 14/9/1752 so I tried changing all the surveys to allow from 1760. Now the CountSurveyRecords report runs, so that's progress, but it only includes surveys which are run by an individual and not those run by an organisation (such as the British Lichen Society or a Local Records Centre) so it's still not much use!

The other two reports still fail because we have a lot of records in our database with date ranges starting either 1700- or 1735- . Is 1752 a fundemental limit? If so I can make a global change to our database, but as there would be more than 100k taxon occurences affected, together with their events, samples and determinations, I would first like to be sure that there is no other way. A limit of 1752 would also give us on-going problems in handling the oldest lichen records, as there were several active recorders before that date.

Janet

The CountSurveyRecords report appears to have an issue if you have any surveys which have a 'Records Allowed From' date from pre 1700 ish.
There's a similar issue with the ProblemDeterminationDates report but regarding determination & sample dates.  Does this sound right based on your data?

Thanks,

Number of records in a survey (CountSurveyRecords) and Determination dates before sample date (ProblemDeterminationDates) both give the error message "Adding a value to a 'datetime' column caused overflow".

Count of records made within date range V07-12 gives the message "arithmetic overflow error converting expression to data type 'datetime'".

These reports are working for other people so could the problem be that I have some duff dates in my database somewhere? If so, any ideas on  what I should be looking for?

Janet