>>I have a remote view wich acceses a single table from a vfp database; some fields are date type.
>>I have two problems:
>>1. When the base table has an empty value for date fields, the remote view shows {31/12/1899}
>>2. An error occurs when I try to send an empty value for a date field { / /}through the remote view.
>>
>>Do I have to deal with this specific date to handle empty data, or is there any solution to make this work in a simpler way (send/receive empty values for date fields)?.
>
>SQL Server has no concept of an empty date - since it has to have a date or a null it makes uup a date and that's why you get {31/12/1899}.
>
>If the field accepts NULL values then send .NULL. when you update the date fields. When you're retrieving data you'll have to deal with the {31/12/1899} as if it's a NULL or empty date.

Thank you very much for your help
Funny thing here is the fact that the remote view is not working against a SQL server database but against a vfp database.

May God help us the day we need to build an app in wich 31/12/1899 has to be considered a valid date!!!