Kevin,
Is it possible that the fields in question are being mapped as Long Varchar2 fields and not simply Varchar2 fields? Longs, in Oracle, are like memos in VFP. They can be up to 2GB in length. However, only one long is allowed per table. It's possible that the remote view is manipulating stuff internally to generate longs and not varchar2s. While it isn't a solution, this may give you more information to work with.

HTH.

>Hello,
>
>I just moved all of the "memo" fields in an oracle table to varchar2(4000) and on my machine I can edit and save all day with no errors (I have a routine that checks for size of text and truncates it to 4000 or whatever the varchar2() size is).
>
>A client has the same routine and on "problem" page there are five memo fields (they went with some smaller sizes than 4000 on some of the fields)
>

>reportto   varchar2(1000)
>ccto       varchar2(1000)
>premable   varchar2(4000)
>bodyoftext varchar2(4000)
>close_text varchar2(2000)
>

>
>If they edit one field (cut and paste a field with more than 5000 characters in it) and save it it -- no problems. If they enter the same text in all five fields and hit save, Tableupdate(.t.) returns .f. and they get the error:
>

>The Error messages are 'Saving of Audit Data Failed'; and '[MICROSOFT][ODBC
>DRIVER FOR ORACLE][ORACLE]ORA-01026: MULTIPLE BUFFERS OF SIZE > 4000 IN THE
>BIND LIST'.
>

>
>The truncation down to 4000 or 1000 or whatever seems to work just fine.
>
>They have MS ODBC for Oracle driver: 2.573.4403.00 while I have 2.573.3711.00. Any ideas on what maybe happening?? -- using VFP6 SP3 dev and Runtime. My next steps will be to
>a) have them install the exact ODBC driver I am using; then I might try
>b) using sql pass-thru instead on updating a remote view.
>
>Of course, it works fine on my machine, which always makes things difficult to fix when you can't reproduce it yourself.
>
>Thanks for any ideas,
>
>Kevin