cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

Here's an odd one.

Environment:

VB.NET Winform

Visual Studio 2008

.NET framework 2.0

Crystal Reports 2008

ODBC connection

I have three reports, living in the same directory. They are essentially identical, except for the grouping. All three run successfully within Crystal reports.

From a report viewer Winform in VS, two of the three run. As I am dealing with a small data set, the reports render quickly. On the third report, There is a long pause when the report viewer form opens, then I finally get an error:

"Failed to open the connection. Details: [Database Vendor Code: 17] Failed to open the connection. CallReportByExtension 58F5C135-7BA3-4215-898A-DADA6C7DAD9C.rpt Details:[Database Vendor Code: 17]

I was initially getting similar errors on all three reports, before changing the datasource location to my ODBC connection. I have double-checked the location, verified the database, etc.

What am I doing wrong? I can provide the VB code if requested, but since the other two reports work properly, I doubt it's code. I do know that I am passing the report name and path correctly to the report viewer form.

As I am about to kick my monitor through the window and become a street denizen, I would greatly appreciate any help that would be offered.

Thanks,

Mike Beckner

0 Likes
View Entire Topic
ted_ueda
Product and Topic Expert
Product and Topic Expert
0 Likes

What type of database? SQL Server?

I'd first recommend looking up error code 17 for you RDBMs system, to get at the root cause. The error message is stating it's getting back error code 17 from the database driver.

Sincerely,

Ted Ueda

Former Member
0 Likes

Oops, sorry...

YES, SQL Server 2000. I couldn't find any direct reference to a code 17.

However, the same ODBC connection works on the other two reports.