Thank you for your help to both of you, I ended up creating a new character field cMyCharacterDate, move the data from dMyBadDateField to the new field,
removed the dMyBadDateField and renamed cMyCharacterDate to dMyNewDate and
changed it to be a date field, the problem went away!

Thanks much!


>>Hello everybody,
>>
>>I'm using VFP8 SP1 and SQL 2000 in the back end, there is one field in
>>one of the tables that keeps coming back "empty" when in the back end is
>>NULL, this causes a conflict; error 1585; when the record is saved.
>>I can't figure out what the problem is, any thoughts on that?
>>
>>I'm using remote views with ODBC
>>
>>THIS.Thankx("In Advanve")
>
>Are you sure it is the empty date field that is causing the error? Normally, empty date values in VFP get stored into SQL Server as "01/01/1900". Unless your table has a trigger that blocks dates with that value, I'd be surprised that it would cause an error.