Oracle Error using CR 9.0 1

[midearth]

We have a report set-up that is connected to an Oracle database thru an ODBC connection. Using CR 8.x, the report runs fine. Using CR 9.0, we receive the following error:

Query Engine Error: 'HY090:[Microsoft][ODBC driver for Oracle]Invalid string or buffer length'

The connect ID to the Oracle database is 17 characters long formatted as: xxxxxxx_xxxx_xxxx

I can't figure out why we don't get the same error using CR 8.5, but do using 9.0

If anyone has seen this issue or knows how to resolve it, it would be greatly appreciated since we're wanting to upgrade to 9.0 without having to make mass changes to the reports or the database.

 

[synapsevampire]

Hopefully you weren't using the Oracle supplied ODBC driver with CR 8.5 as it will return bad results, you should have been using the CR supplied ODBC driver.

consider changing the connectivity to native anyway as it's muhc faster:

Database->Set Location->More Data Sources->Oracle Server->and point at the first table, the system will prompt you to propagate changes to the other tables, say yes.

-k

 

[midearth]

Thanks k. I've tried setting the database location to no avail (still get prompted for the sign-on and it kicks back the error message). We're actually using the Microsoft ODBC driver for Oracle. Never had any luck using the CR supplied drivers. I don't know if native connections will work since we're actually accessing an Oracle database server in another state thru the web.

 

[Turkbear]

Hi, If ODBC works, then Native will..It is an overlay to the native stuff, which it uses to make the actual connection.

 

[midearth]

Thanks for all of your help. I got the reports to work just by switching to another Oracle driver.

 

[cathey04]

What oracle driver did you switch to? I am having a heck of time too.

 

[midearth]

I had originally set-up the ODBC connection using "Microsoft ODBC Driver for Oracle". Report ran fine using 8.5 but not 9.0. I removed that connection and changed it to "Oracle ODBC Driver" (note - not the MS version driver). Haven't had any issues since.

 

[midearth]

Before you go through the process of changing your datasource, you may want to download the latest service pack for Crystal Reports 9.0 if that's the version you're running and haven't done so. I downloaded the SP a few days ago and just changed my database connection back to the original to see what would happen and the report ran fine without any error messages.