Thanks for the info Tim. It turned out this was not the problem, but it pointed me in the right direction. VFP remote views have a 'feature' that allows the size of the field to be changed. If the field size in the view is larger than the actual field size this error will occur when the user enters more data than allowed. For example, if you have a field that is VARCHAR(2) and the VFP view shows CHAR(3), attempting to update the table will fail with the ORA-01084 error.

Also, I did test a LONG field by placing over 128K of data in it via the VFP view without problems. In what did you see this error and what ODBC version were you running?



>The problem is something to do with the fact the the LONG type is only max.
> 32K in length, while the LONG type in database storage is nearly 2G.
>
>What SQL are you executing my best guess is to not include the field in the update
> if the memo is empty. Or you may want to try to change the table type from LONG to varchar(4000) or BLOB depending
>on what you are putting in it.
>
>What I do is use varchar(4000)'s for memeo fields and create the sql like:
>If that doesn't help give me the table structure and if the memo fields are empty or not?