It's not that they are incompatible, it's just that SQL Server has no concept of what an empty date is. You should make the tables accept nulls and program accordingly.


>I have an almost completed application that uses SQLServer to store data and VFP8 cursoradapters to edit the data. I solved all problems with one exception - VFP and SQL Server date/datetime data types incompatibility.
>VFP empty dates are converted to "1900-01-01" values while saving. When I refresh the cursor user can see "1900-01-01".
>I can use NULL values on both sides (VFP and SQLServer) but it leads to additional more complicated VFP code ( ISNULL, NVL() etc... inside forms and reports methods).
>For me the best way would be to convert SQL Server "1900-01-01" and NULL values to empty VFP dates and vice versa but I can find the good idea how to make it happen without hurting application performance and without writing too much additional code. All ideas are welcome.