>I think I may have missed the point you were previously trying to make to me in your original suggestion.
>
>Obviously if the remote view cursor field width is limited to the exact same width as the data to be updated right from the outset per your code change, then there can be no space for any pads in the updated result - I guess that is what you were suggesting and that certainly is worth trying. I apologize for missing that.
>
>Thank you very much for taking the time to offer ideas. I'm very grateful to have your support.

You're welcome.

As a general rule, when I'm moving data between disparate systems I try to make the data types identical or as similar as possible. With the new varchar, varbinary and blob VFP types, and the CAST() function in VFP9 we have more and better options to do this than with earlier versions.

Another thought just came to me - VFP Remote Views are based on ODBC, in your case the ODBC Driver for SQL Server. If you continue to have problems, check the version you have. If it's old you could try the current one in the MDAC 2.8 SP1: http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&DisplayLang=en