I'm working on a project where the client needs to generate their own custom reports. Every time they create a new report, they don't want to have to recompile and redistribute the entire application to every desktop in the company.
For this reason, we went with Crystal Reports, since its external *.rpt file capabilities seemed the perfect solution to our problem. But now we're having problems with the crystal reports.
Each report is generated using one (or possibly more) stored procedures on a SQL Server 2000 database. When being developed, the report developer uses a development server, so any mistakes they make won't affect the live server.
We wrote a small report-viewer application using the Report Viewer Control. The problem we're having is that when the report is opened in the viwere application, we need to connect the report to the _LIVE_ database server, even though it was developed and tested against the development database server.
The database name, table structures, and stored procedures are identical on both servers (although I realize the objectIDs are different, and am wondering if that could be the problem.)
The report viewer application should not take any part at all in building the dataset used in the report. Everything that is different from one report to the next should be entirely contained within the report and its accompanying stored procedure.
Any suggestions on how to sove this problem?
BTW, we're developing in VB6SP4.
Thanks
--
Calin
MCDBA, MCSD, MCP+SB
For this reason, we went with Crystal Reports, since its external *.rpt file capabilities seemed the perfect solution to our problem. But now we're having problems with the crystal reports.
Each report is generated using one (or possibly more) stored procedures on a SQL Server 2000 database. When being developed, the report developer uses a development server, so any mistakes they make won't affect the live server.
We wrote a small report-viewer application using the Report Viewer Control. The problem we're having is that when the report is opened in the viwere application, we need to connect the report to the _LIVE_ database server, even though it was developed and tested against the development database server.
The database name, table structures, and stored procedures are identical on both servers (although I realize the objectIDs are different, and am wondering if that could be the problem.)
The report viewer application should not take any part at all in building the dataset used in the report. Everything that is different from one report to the next should be entirely contained within the report and its accompanying stored procedure.
Any suggestions on how to sove this problem?
BTW, we're developing in VB6SP4.
Thanks
--
Calin
MCDBA, MCSD, MCP+SB