>>>>Hi,
>>>>
>>>>I received an error message from a customer who uses my VFP 9 application with SQL Server 2008 database. The error message says "Datetime field overflow." What could have the customer done to create this type of error? or could it be SQL Server database corruption?
>>>>TIA
>>>
>>>I was able to duplicate. I can enter date, 12/12/1007 in the DATE field of the application and it generated the error as in the title. So I have to just enter some validation to prevent it.
>>
>>I figured it was an out of range issue. Earliest date supported is 1753, I think? I'm too lazy to go goggle it, but it has to do with the range and the Gregorian calendar.
>>
>>Maybe that's been addressed in more recent versions, I honestly don't know. I'm sure if I had to store historical dates before 1753, I'd know the answer. :)
>
>I recently found an online article about the village where my father was born and raised and even that article started the dates from the beginning of 19th century. But my customers like to "manipulate" the dates (confusing the ever vigilant IRS) by entering early dates :)

I just realized, good thing I've never had to enter JB's date of birth - might have a problem. :)

(Just kidding, John)