One of the options in the ODBC DSN you set up for your data source is
Use ANSI nulls, padding and warnings.

You can experiment with this setting to see if it changes the way trailing blanks are stored.

I think SQL Server by default will trim any trailing blanks and this would happen regardless of how ODBC sent the data. There may also be a setting in Oracle to determine this behaviour.

Some people have complained about just the opposite (no spaces when they want them.

>VFP 5 & 6 seem to put trailing spaces on the end of any char field. It shouldn't do this and I don't know why it is doing this. Does anyone know if there is a setting to shut this off?