>Has anyone came up with a fix for the problem with the VARCHAR2 data types in Oracle. Remote Views in VFP will always pad the field with spaces. I have several tables that have the key field as a VARCHAR2 in Oracle. I can not use remote views to update the Oracle data because '123' and '123 ' don't match! I can use SPT to update the tables and ADO seems to work but I really want to use remote views.
>
>-David-
Don't know if this will work for your situation but it did for me even though it certainly wasn't my choice - the powers to be refused to change anything in the Oracle database so I was stuck with their PK's which were varchar2. All of the values were either 6 or 7 characters in a 10 character field. I had to create 2 views -one with a PK width of 6 characters and one with 7 characters - divide my updates according to the length of th PK value then do my updates for each. Sounds screwy but the bottom line is that the values in the Oracle table were not padded.