>I was curious if you ever ran into a situation where a VFP 7 Remote view always pads the end of a string with spaces? That is say I have a VARCHAR(30) on SQL Server and pull down a row of data that contains 'Pen' - or 3 characters of
>data. If this data is pushed back (saved) from VFP 7 to SQL Server 2000 it is going in as
>
> 'Pen' + SPACE(27) instead of just 'Pen' - no trailing spaces.
>
>Of course, this defeats the purpose of a VARCHAR. Is there a way to make the VFP remote views work without adding the trailing spaces?

Tom,

If you a retriving the data into a remote view, which only supports charater data type, even if the data was trimmed on the server then it would be padded in the remote view.

That being said, the CA does allow for trimming the fields before they are sent to sql.

BOb