Claude,
We had this issue as well. Two suggestions:

1. Convert Key fields to number/integer data type.
2. Convert Key fields to Char data type instead of Varchar.

Most likely option 1 is very work intensive. However, option 2 is very straight-forward. Data will be padded in Oracle as well as VFP and you shouldn't have a problem. Of course it will take up more space within Oracle, but hopefully, that's okay.

HTH.

>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.
>
>>What kind of return value do you get from the TABLEUPDATE() command? If it is less than zero, you need to check AERROR() to see what kind of error messages you are getting back.
>>
>>>I can make changes to small tables but I lose all the changes for large tables. Any suggestions?
>>>
>>>Claude
>>>
>>>>Yes
>>>>>are you doing a TableUpdate??
>>>>>x = TableUpdate(.t., .t., viewname, aerrorarray)
>>>>>
>>>>>If you're not doing this yet I'd take a look at the help on the tableupdate command. There are also some things to consider about row or table buffering....
>>>>>
>>>>>>I created an remote view to an Oracle table. I have selected key fields that uniquely identify each record,selected the update fields that I need and I have "Send SQL Updates" checked off. But when I make changes to the tables they are not reflected in the oracle table. Then if I try to browse the table again I get an update conflict. Any suggestions?