1 Topic by Purgle Linham

  • Purgle Linham
  • Veteran
  • Offline
  • From: Wiltshire
  • Registered: 30-03-2009
  • Posts: 99

Topic: Future dates importing

Hello
I recently came across some rogue date ranges in Recorder 6 (v 6.18) where the second date was in the future and this had been caused by Excel changing the last digit of the date range. As this annoyingly wasn't picked up at the time these had been imported using the wizard, had been revalidated along with the entire database and had been validated again using the Problems V2 xml report and at no point flagged as incorrect. So I'm curious to know how they got in and why they weren't picked up subsequently.

Thanks
Purgle

Purgle Linham
Wiltshire & Swindon Biological Records Centre

Purgle Linham's Website

2 Reply by RobLarge

  • RobLarge
  • RobLarge
  • Veteran
  • Offline
  • From: Wiltshire
  • Registered: 15-07-2008
  • Posts: 812

Re: Future dates importing

I have done a bit of checking & this is not just an import issue. If I try to create a survey event with a date range like 01/01/2000-01/01/2025, i.e. where the end date is in the future, Recorder does not object and saves the event.

Is this normal behaviour, because I can't see how it is useful if it is. In Purgle's example above a bit of sloppy excel data entry lead to the successful import of several records with invalid date ranges and these were not picked up by any of the other checking mechanisms.

Rob Large
Wildlife Sites Officer
Wiltshire & Swindon Biological Records Centre

RobLarge's Website