on 02-19-2014 11:16 PM
I'm running Crystal Reports 2008 (version 10.5.0.0) on Windows 7 64-bit. Using the 32-Bit Data Source (ODBC) link under the Crystal Reports 2008 program directory, I've set up a User DSN (and System DSN) to the oracle database with the driver provided by the Oracle client (Oracle in OraClient10g). I can successfully test connect from there. However, when I run reports (created in CR 11.0.0.895) I run into the following error.
I see lots of discussion about 32-bit/36-bit ODBC as problematic. I was wondering if it might be an issue with the version of Oracle client I'm using (32-bit 10.2.01) and a newer client might resolve the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually, the error above points to an OleDB driver, not ODBC - the two are different. However, is there a specific reason why you're using an ODBC connection and not the Native Oracle connection that's available through Crystal? I have found the native Oracle connection to be MUCH more stable and reliable than ODBC in the (many) years that I have been using Crystal.
-Dell
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.