>>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
>
>
>It could be a bad/out of range value. I'd try to get some more specifics (and see if you can recreate it with an out of range value)
>
>Also....what is the actual data type (date time type) being passed, and what is the specific data type in the actual sql database?
The field type in SQL is DateTime. But the type in the VFP application is DATE. The application is using CursorAdapter to get/set values from VFP to SQL Server. Usually VFP won't allow me to enter a "bad" date so I wonder how (if this is the case) the customer was able to enter an invalid date. I will have to try to simulate entering bad date in the VFP to see if I can duplicate the error.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
