Sally,

That certainly sounds possible - any way of finding the culprit record, as I mentioned there are 100s of events in the offending survey!

Data Entry – Enter a species record in R6 v6.13.3.182 allows users to input an species observation with a date of say 15/04/2008 but with a date of determination of April 2008, 2008 or Unknown. The problem is that if the survey is then revalidated these are flagged as invalid because the determination date cannot come before the sample date. Vague dates are held in the database as a start date, end date and date type so that reports can be produced in date order etc., and the start date for April 2008 is 1/04/2008 which is before 15/04/08. The start date for 2008 is 1/01/2008 and for Unknown the start date and end date are both 0. Either Data Entry – Enter a species record should block determination dates like these or they shouldn’t fail revalidation. The same problem can occur when entering data via a recording card.

A further problem is that if you then export the survey without correcting the invalid items and reassign custody to another Site ID the system sets the custodian on invalid items to the specified Site ID and they can no longer be edited, even though the invalid items aren’t exported. The same happens whether you use Tools – Export data or do the export using a filter. Either custody shouldn’t be reassigned on invalid items or they should be included in the export so that they can be corrected in the receiving system.

If a habitat observation is input at the same time (date 15/04/2008 and date of determination April 2008) then revalidating the survey fails with the error message below although if the determination date is changed to May 2008 revalidating works. If the survey only contains a small number of habitat observations they should be easy to find and correct, but if anyone is having difficulty locating the problem observations let me know as I have written a xml report to list habitat observations with their determination date before their sample date.

date/time         : 2009-02-16, 12:42:05, 984ms
computer name     : SONYVGN-S5XP
user name         : Sally Rankin
operating system  : Windows XP Service Pack 3 build 2600
system language   : English
system up time    : 45 minutes 46 seconds
program up time   : 26 minutes 59 seconds
processor         : Intel(R) Pentium(R) M processor 2.00GHz
physical memory   : 292/1022 MB (free/total)
free disk space   : (C:) 9.02 GB
display mode      : 1280x800, 32 bit
process id        : $24c
allocated memory  : 22.79 MB
command line      : RecorderApp.exe /327986
executable        : RecorderApp.exe
exec. date/time   : 2008-11-04 08:45
version           : 6.13.3.182
madExcept version : 2.7h
exception class   : EOleException
exception message : List index out of bounds (0).

main thread ($20c):
00917a72 RecorderApp.exe FormActions 1883 TdmFormActions.RevalidateNBNData
009176bc RecorderApp.exe FormActions 1806 TdmFormActions.RevalidateNBNData
00917630 RecorderApp.exe FormActions 1784 TdmFormActions.actDatabaseValidateSelectedExecute
00451c23 RecorderApp.exe Classes          TBasicAction.Execute
004bf301 RecorderApp.exe ActnList         TContainedAction.Execute
004bffa3 RecorderApp.exe ActnList         TCustomAction.Execute
00451af7 RecorderApp.exe Classes          TBasicActionLink.Execute
004c5a7f RecorderApp.exe Menus            TMenuItem.Click
004c6d33 RecorderApp.exe Menus            TMenu.DispatchCommand
004c7aba RecorderApp.exe Menus            TPopupList.WndProc
004c7a09 RecorderApp.exe Menus            TPopupList.MainWndProc
004528d8 RecorderApp.exe Classes          StdWndProc
7e4196c2 user32.dll                       DispatchMessageA
004d4de3 RecorderApp.exe Forms            TApplication.ProcessMessage
004d4e1a RecorderApp.exe Forms            TApplication.HandleMessage
004d503a RecorderApp.exe Forms            TApplication.Run
0099f832 RecorderApp.exe RecorderApp  317 initialization