Try making the Oracle column a varchar2(2000) instead of varchar. Varchar was the predecessor to varchar2 but was kept for backward compatibility. Second, I recommend using the MS ODBC Driver for Oracle instead or Oracle's drivers. See if those 2 suggestions will help.

>I've got a form which uses a remote view I created from one Oracle table. I've got controls (in this case an edit box) on my form which are using fields from this remove view as datasources. I'm using the TableUpdate() function to commit the changes from the remove view to my Oracle table.
>
>Just recently I was required to allow the user to delete the contents of an edit box which is bound to memo field in my remove view. On the Oracle end of things that column is actually a varchar(2000), but since VFP doesn't support character data types with a length greater than 254 I had to use a memo field in my remote view.
>
>Here's the problem: The user clears the contents of the edit box (and it's controlsource). I then attempt to commit the changes to that record using the TableUpdate() command. I receive a few different errors:
>'SQLExecDirect with return code 99 (SQL_NEED_DATA)'
>'[ODBC]No data at execution values pending. (0)'
>
>I've tried setting the field to .NULL. before issuing the TableUpdate(), but I get these errors:
>'SQLExecDirect with return code -1 (SQL_ERROR)'
>'ORA-01084: invalid argument in OCI call'
>
>I may be overlooking something really obvious, but I'm stumped as to what to do. I haven't been able to find any information regarding this problem anywhere I've looked. Any help would be greatly appreciated. Thanks.
>
>Corey

Mark McCasland
Midlothian, TX USA