Crystal Reports/Crystal Viewer and VB.NET
- From: Mannkind <mannkind@xxxxxxxxx>
- Date: Wed, 01 Aug 2007 03:21:46 -0000
Before posting my problem, here is some background (information that I
think might be requested if I don't include it).
The Machines:
* Production (+CR9 Redistributable Runtime Stuff [Crystal
Viewer?])
* Development (+Crystal Reports)
Software in Use:
* Windows XP
* Visual Studio 2003
* SQL Server
* VB.NET
* Crystal Reports 9 (Developer)
The Report:
* Stored on a networked drive, accessible via Development and
Production machines.
* Connects via ODBC (ODBC available on both machines, exactly the
same) to the SQL Server database
* Takes 2 parameters
* Works _great_ in the Crystal Report Designer (on the Development
machine)
* Works _great_ in VB.NET+Crystal Viewer (on the Development
machine)
* Does _NOT_ work in VB.NET+Crystal Viewer on Production Machine
(produces the dreaded 'rowset' error)
VB.NET:
* A form that has a CrystalReportViewer.
* Loads the specified report, passes 2 parameters
* The report (should) appears w/ a print dialog.
The Problem:
The problem is that I am not sure what the heck is wrong. The report
works great on the development machine when ran directly within
Crystal Report Designer *or* called by the VB.NET.app within Crystal
Viewer.
However, once I deploy the VB.NET app to the Production machine and
try to run the application I *always* receive the following error,
"failed to open a rowset" exactly twice. After clicking 'Ok' the
CrystalReportViewer remains opened but blank, until closed manually.
Things I Know:
I know both Development and Production computers can reference the
report correctly (and in the exact same manner)
I know the ODBC connection is working (on both computers) because I
can use it manually/otherwise.
I know the Production box has the required CR9 Redistributable Runtime
Stuff [Crystal Viewer?] files because if I uninstall it the VB.NET
applications errors immediately.
I know the Report is correct because I have had Crystal Reports verify
the database.
Well, I don't know what other information might be helpful. I hope
I've included enough background information to help diagnose the
problem.
.
- Next by Date: Crystal Reports for Visual Studio 2005 error in Managed Assembly, HELP!
- Next by thread: Crystal Reports for Visual Studio 2005 error in Managed Assembly, HELP!
- Index(es):
Relevant Pages
|