>>>Thanks Cetin.
>>>
>>>It seems when I used the DATE type in SQL Server it copied over fine but when I ran the remote view I got Error 2005, a conversion issue. When I disconnected the remote view and ran from local tables the error remained the same. ???
>>>
>>>I think the datetime type will work and it seemed to display OK on the VFP forms in the Date field. The only issue was that it rejected any bad date and some date arithmetic code has to be changed. Any further suggestions would be appreciated.
>>>
>>>Regards,
>>>
>>>Bill
>>
>>Date is too just fine, provided you don't use old drivers. I forgot to tell, I am using OLEDB and ADO as much as I can. MS SQL server will drop OLEDB in future, but as of now, that is the only reliable driver to work from VFP. Use ODBC only if you have to (the era of SPT and remote views are closed long ago IMHO).
>>(if you can search, I posted codes that demonstrate with ODBC drivers there are problems with fields like varchar(max), varbinary(max). One of these bugs were corrected in VFP9 SP1 if I remember right - otherwise any varchar\varbinary over 8000 was lost)
>
>Devart ODBC drivers provide almost full featured field mapping between MSSQL and VFP. (including Varchar(max), read as Memo, and Varcbinary(max), read as Blob).

Hi Antonio,

PMFJI. So far my customers have been using the ODBC driver that comes with Windows. But, just in case, I run into an issue with the Windows ODBC in the future, I would like to know more about what you mentioned, Devart ODBC. So my newbie question, please, if you were to use Devart ODBC it has to be installed on every PC/desktop using the VFP application? And, can some desktops use the "standard" Windows ODBC and some use the Devart ODBC?