I never tried with XP, only Win7.

>Ok, I looked with him again. Somehow he was using SQL Server Native Client. When he changed to SQL Server driver, it worked for him just fine.
>
>I am not sure why he didn't catch it earlier.
>
>So, using SQL Server driver for Windows XP does work for varchar(max) columns while SQL Server native client does not work.
>
>
>>>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.
>>
>>I don't think there is any solution to this problem. Personally I had to switch to using Text fields instead, they will map to Memo fields in VFP.