>>'Set date' command in VFP6 & VFP7 behave a bit different
>>This is a note I cut & paste from VFP7 help
>>"Note: When SET DATE is set to SHORT or LONG, a date before {^1601-01-01} is invalid and generates an error"
>
>Herman,
>
>Thank you for the heads-up. I'm "glad" to see that this new feature is at least documented in the help file. I wonder what happened on that day historically to make VFP7 cringe in disgust.
>
>Well, now the obvious problem we have is that this new feature will crash our application if a user makes a typo in entering a date. One idea I had for a workaround is to use ON ERROR in our date textbox control to try to trap the invalid date/datetime value error.
>
>If anyone else has any other ideas to address this issue, feel free to suggest!
>
>Laterness,
>Jon

"What happened in Rome between October 4 and Oct. 15, 1582(?) ?"

"Nothing - these dates didn't exist."

Before that date, the Julian calendar was used. After that date, the Gregorian. After Thursday, Oct. 4, followed (by decree, of Pope Gregor XIII) Friday, Oct. 15. IOW, before 1582(?), the Gregorian Calendar didn't exist. VFP preferred to "cringe in disgust".

Perhaps you should store dates in numeric fields, or something similar, if you need to go back in time that much.

Hilmar.