LONG (varchar) & binding on Oracle8.0.5 & PB6.5

Anybody, please help. Our shop is currently adding Oracle support to our app
(Win 95/NT, PowerBuilder 6.5, Oracle 8.0.5, ODBC drivers only). There are
several issues wrt long varchar fields and Oracle, but I can't resolve the following:

1. It won't let me confirm a string field with more than 4K bytes (but less than 32K) of text back to Oracle database (via Update() on a datawindow). The related field in the Oracle database is LONG datatype, i.e. PB's dw object sees it as a char (32K) field. The error I get is: "SQLSTATE = S1000 [Oracle][ODBC][Ora]ORA-01704: string literal too long".

In this case the binding is turned off (DisableBind=1).

Also, if I try to stick the same string value to database directly via Oracle's ISQL (SQL Worksheet) I get the same message: "ORA-01704: string literal too long".

So, the $1M question is: How to Insert/Update a string literal values larger than 4K bytes (and less than 32K) from dw objects and via SQL script? Perhaps some Oracle server setting is not configured properly???

2. If I turn the binding on (DisableBind=0,StaticBind=1) and I try to insert and save the text field with more than 4K bytes of text (but less than 32K) then I get the following error: "Bind parameter value for ':1' is too big
(4248). No changes made to database."

But the related field is recognized as a char (32K) on PB datawindow object and it is LONG in Oracle's database. I also get this message even if the string value in the field is less than 2K bytes.

3. If I turn the binding on (DisableBind=0,StaticBind=1) and I try to insert and/or save a row then I get the following message: "SQLSTATE = 07001 [Oracle][ODBC][Ora]ORA-01008: not all variables bound". Any ideas???

Thanks in advance for your help.

Juraj Received on Tue May 11 1999 - 13:29:16 CDT