SQL Server varChar(max) field adds spaces to VFP Memo field in remote view

Sounds like a Unicode conversion error. Imho the backend column should be NVARCHAR(MAX) instead.

Sadly ste5an, that did not resolve the issue.  Thanks though.

Well, use SSMS to look at the data. It's possible that you already have bad data. So you need to redo your data copy task.

Data's good.  Oddly, if I have both a varChar(max) and an nvarChar(max) field in the server database I'm able to access the varChar(max) data without issue.  Go figure?  Hoping that's the "solution."  Thanks for the help!

It still sounds like you have both VARCHAR and NVARCHAR fields and assume some NVARCHAR fieds to be varchar, while they're not.
Or you (or "something") even converted text on the client side to Unicode before storing it to Varchar, thus storing unicode in non unicode fields.

For how VFP retrieves data as Unicode or Ansi also look into SYS(987) and mapvarchar setting of the connection.

Besides all that the SQL Server ODBC driver series works better in VFP than SQL Native Client ODBC, especially SQL Native Client might give you Char(0) fields instead of VFPs varchar(max) equivalent of Memo fields, even though char(0) is a column type you can't create with CREATE TALBE or CREATE VIEW yourself. There is some mismatch of VFP and ODBC at work here, maybe.

Bye, Olaf.