Re: Oracle ODBC question/problem?

That's pitiful. All they need to do is write a tiny C program using the ODBC API and attempt to pull back any column defined as NUMBER(18), for example. There's no excuse for Oracle needing a code sample to fix this problem.

Thanks for letting me know I'm not alone and the recommendation of the last 'good' driver.

--
Regards,
Jim
No Body wrote in message <35EA8CA8.F43E7586_at_Email.com>...
|Try using Oracle ODBC 1.16.3.10.
|We had a similar Problem using Powerbuilder. This is the last ODBC-Driver
that
|works :-( ... Oracle is still (almost a year) waiting for a Test-Case from
|Powersoft....
|
|
|Jim Morgan wrote:
|
|> We are having a problem with an ODBC application we have written in MS
|> Visual C++. The ODBC calls we use are strictly C ODBC API calls. Our
|> client application runs on a Win95 or NT4 client and connects to an
Oracle
|> 7.3.2.3 database on AIX.
|>
|> We have several fields in our Oracle tables defined as NUMBER(18).
Whenever
|> we try to pull some of these values out of the database, we get an error
if
|> the number itself in the database is more than 10 digits. The error is
|> returned from the Oracle ODBC driver. If we use the Intersolv ODBC
driver,
|> we do not get any error and everything works fine.
|>
|> There are two things I'm curious about: what exactly is the Oracle driver
|> doing, and how can I get around it. It appears the Oracle ODBC driver is
|> always trying to put numeric database columns into a numeric (int?)
|> variable, and when the numeric value is too large for the int variable to
|> hold, we are getting an error. We surmise the Intersolve driver is
putting
|> the data into a character host variable and then doing some sort of
numeric
|> conversion.
|>
|> The native error returned by the Oracle ODBC driver is 1455 ("converting
|> column overflows integer datatype").
|>
|> We can get around this problem by redefining the database column to be
|> VARCHAR2 instead of NUMBER, but our software is installed at several
|> customer sites so that is only a last resort. Our customers would rather
|> use the Oracle ODBC driver because the Intersolv driver is so much more
|> expensive. We make only core ODBC calls in our application, so the extra
|> support in the Intersolv drivers is not something we need.
|>
|> Any information is greatly appreciated.
|> --
|> Regards,
|> Jim
|>
|
Received on Tue Sep 01 1998 - 19:53:52 CDT