ODBC

General development discussion.

Moderators: Susan Smith, admin, Gabriel

Gabriel
Posts: 371
Joined: Sun Aug 10, 2008 7:37 am
Location: Arlington, TX
Contact:

ODBC

Postby Gabriel » Thu Jan 03, 2013 11:05 pm

I'm trying to configure Crystal Reports and get it to connect to a BR ODBC Data Source using BR's ODBC driver. I believe I have the dictionary properly entered into context but its possible that this is where my mistake is.

Crystal Reports can see the BR data source just fine. The Crystal Reports Report Wizard shows me a list of the tables (data files) in their system. Most of the files contain both strings and numeric fields, but a couple contain only string fields.

If I try to select a file that has numeric fields in it (usually BH), I get this error: "Database Connection Error: '22003:[ADS][BRODBC Driver]Out of range [Database Vendor Code: 1011 ]'"

If I try to select a file with only string fields in it, Crystal Reports accepts the selection and the Report Wizard completes as normal. However, as soon as Crystal Reports tries to display the data on the screen (in their Report Preview window), Crystal Reports crashes.

I have one file in my system that has only strings, and the data file is empty. That file works fine, and Crystal Reports displays the completed empty report. This leads me to believe that its failing when the data is being sent to Crystal Reports.

I'm using the latest ODBC, and the latest Crystal Reports, CR 2011. I downloaded the demo from their website a couple days ago. .

I know some of you are using ODBC .. has anyone run into anything like this?

If I am missing some key piece of information in context, where should I start looking?

GomezL
Posts: 232
Joined: Wed Apr 29, 2009 5:51 am
Contact:

Postby GomezL » Fri Jan 04, 2013 11:02 am

PROBLEM: User is attempting to use crystal reports with ODBC the users
gets error DATABASE CONNECTOR ERROR: "22003:[ADS][BRODBCDRIVER]OUT OF RANGE [DATABASE VENDOR CODE:1011] when they attempt to access a table.

RESOLUTION: In Crystal Reports, there are several ways to connect.
**MAKE SURE ODBC DRIVERS ARE CURRENT Ver. 4.01.00.00**
Make sure they use the "ADO - ODBC" interface, and NOT the ODBC choice (For some reason, crystal calls it something different).
** Note: Some versions of Crystal reports won't work in any case, so create "VIEWS" in MS-Access and use the MS-Access database to create Crystal Reports

Gabriel
Posts: 371
Joined: Sun Aug 10, 2008 7:37 am
Location: Arlington, TX
Contact:

Postby Gabriel » Fri Jan 04, 2013 4:01 pm

Do you mean, make sure BR's odbc driver is the latest version? Or did you mean make sure Crystal Reports' ODBC driver is the latest version? How can I check the version number of the ODBC driver?

When I select ADO, it gives me another list of things to choose, and one of those is ADO for ODBC.

Using the ADO ODBC driver, I get slightly better results then I did with the straight ODBC driver. I can now select files that have numeric fields in them, which I couldn't do before. But Crystal Reports still crashes when I go to display the data..

GomezL
Posts: 232
Joined: Wed Apr 29, 2009 5:51 am
Contact:

Postby GomezL » Fri Jan 04, 2013 4:34 pm

Version is specific to the ODBC drivers. It's somewhat hard to check version, but in the ODBC control panel, there is a Drivers Tab, this can help Check the version.

Crystal is sometimes "Ornery", so make sure your queries work in MS-Access before you attempt to use Crystal. (MS-Access is much more forgiving).

Our practice is to create an MS-Access Table with "Views/Queries", and then we use these View/Queries in Crystal, this combination seems to work best. (MS-Access "Cleans UP" the Crystal Queries").

Finally, use the "Logging" feature to see what's going on.


Return to “General Development”

Who is online

Users browsing this forum: No registered users and 2 guests

cron