There are lots of issues with the SQL Server native client when you connect from FoxPro. I think the problem is that the ODBC driver uses newer types that aren't supported by FoxPro and that causes problems. I seem to remember similar issues with Dates (vs DateTimes) and XML fields. The regular SQL Server ODBC driver tends to work better all around but there are a few things that don't work with it that work with the SQL Native Client. So neither one of the solutions offers 100% compatibility of the supported features unfortunately and which is which is not documented anywhere.

In my experience though I've been using the SQL Server driver which works with the most of the stuff I care about.

+++ Rick ---

>Hi everybody,
>
>My colleague is having a problem with our application. We have Settings table where the SettingVal column is varchar(max). He is using Windows XP computer and the settingVal column is not updated for him (remains blank). The statements being passed from VFP to SQL Server use this syntax
>

>execute sp_executeSQL "update dbo.Settings set SettingVal = @p1 where KeyVal = @p2", N'@p1 varchar(max), @p2 int', '', 100
>

>
>So, for some reason the value is not passed in correctly.
>
>Needless to say that it works OK for everyone else. I compared our ODBC DSN settings and the difference is that I am using Microsoft SQL Server ODBC Driver Version 06.01.7601 and he is using 03.85.1132 version. I suspect that this is the problem unless you can think of another one.
>
>Now, we did a quick Google Search for ODBC Sql Server Driver for Windows XP but we didn't find a link to download the driver which will work on Windows XP.
>
>Do you know where he can get the driver?
>
>Thanks in advance.