Move to VFP9 where you can now use varchar data types in VFP views, etc. Otherwise, in VFP8 use CursorAdapters and take advantage of the ConversionFunc property to specify which view fields to RTRIM when the data is sent back to Oracle.

I have a CABuilder that you can get from http://www.mctweedle.com that will help you. Just click the FoxPro Tools link from the main page.

>The back end database used by the company I work is Oracle. They use VARCHARs extensively. I am going to be migrating all of my tables into the existing schema. We are basically mergin a number of products into one larger configurable product suite. But remote views only let me choose CHAR and from what I have seen so far the data is padded with spaces to the length of the field.
>
>For instance I had a generated key table that has a 2 fields.
>
>FIELDID CHAR(8)
>LASTUSED CHAR(20)
>
>I moved the table into ORACLE using varchars. Previously he parameterized view worked when given an unpadded parameter. But when moved to oracle I had to pad the parameter with spaces for it to work.
>
>Does anyone have any suggestions?
>
>The other developpers want me to find a way to remove the extra padding that is sent to the VARCHARs.
>
>Any ideas?
>
>Jason