Thanks for the reply.

I am one of many who uses these tables therefore I must leave them the way they are.

The PK in most tables is a varchar2 of 18 char but the data is actually only 15 char long. So when I created my view I was able to set the field to 15 char and do my work.


>It actually has to do with VFP adding the trailing spaces in character field values which get sent back to Oracle. The actual data in Oracle most likely has no trailing spaces [VARCHAR2]. So you get no matching rows when that value is in the WHERE clause. If you need a character field as a PK, then use the CHAR data type instead of VARCHAR2 in the Oracle table. You would not have this issue if your PK was numeric.
>
>>What I found is that the key fields must be have the exact size of the table structure definition.
>>
>>Ex: if the field ID is a Char of length 20 and is delegated as a key field in the view then I can only update records that have a id of length 20. If the id record is of length 19 or less then the update craps out. It seems like an SET EXACT problem. Any Suggestions.