>Mark,
>
>I was experimenting with the triggers and found something interesting. I was under the impression that my trigger was creating a second update and causing an update conflict. After removing the trigger I was still receiving an error when issuing the tableupdate with a force value of .f.
>
>Here is what I think is happening. Say the value of the field in the Oracle table is trimmed. When foxpro creates a cursor from that record that field in the cursor has the padded spaces. Consequently when you issue a tableupdate with a force value of .f. foxpro compares the oldval of the cursor to the oracle field value and the two are different thus generating an Update Conflict.
>
>Do you have these same problems in you apps?

Basically that is what is happening. An Oracle varchar[2] data type typically does not store data with trailing spaces. Once the Oracle table is forcibly updated with the data from VFP, you should notice that the records updated in the Oracle table now have data RPADded with spaces. Any future updates to those values will not have the update conflict problems unless you go back and rtrim manually before the next update. Since the values are now padded with spaces, VFP has in effect made those CHAR data types.