Re: Code that worked now broken w/oracle 8 and ODBC 3

I doubt that Simba 16-bit ODBC driver is ODBC 3.x compliance. If that is the case , you can't use ODBC 3.x API in your application.

David Bush <kawika_at_hawaii.rr.com> ¦¸¼g¤J¨ì¥DÃD <34DF7F86.16E983A2_at_hawaii.rr.com>...
> Code that worked with Oracle 7 and ODBC 2, now does not work with Oracle
>
> 8 and ODBC 3.
>
> I'm taking an "error in assignment" error when executing SQLExecDirect.
> It only happens with calling a stored procedure with SQL_NUMERIC output
> parameters. A numeric input parameter will work as will other types of
> output paramters. As an example, the SQLBindParameter for one of the
> numeric fields looks like this:
>
> holder = 0;
>
>

SQLBindParameter(hstmt,2,SQL_PARAM_OUTPUT,SQL_C_CHAR,SQL_NUMERIC,10,0,TheVal ue,64,&holder);
>
> TheValue is a pointer to a "2".
> The parameter is definde as NUMBER(10).
>
> I'm using the Simba Oracle 8 driver.
> The application is a 16-bit Borland C++ OWL app.
>
> Why the difference between ODBC 2 and 3?
>
Received on Tue Feb 10 1998 - 00:00:00 CST