refresh parameters after installing maintenance release 1

phuctran · Sep 10, 1999

Hi all, 
 
I have around 150 reports and they worked fine before I installed Crystal Report Maintenance Release 1 on Aug, 99. 
 
I already tested the problem this way: created a new server which had old version of Crystal Report (CR7.0) and tested my reports; They worked fine. Then I installed the Maintenance Release 1 on that server, my reports just uses the default parameters even though I pass new parameters in. 
 
I called Technical suport, they told me to check some ASP code to make sure not using cache. I did all things they told me (even more), but it does not help. 
 
This is what I have done so far: 
1. Uncheck File¦"Save report with data" 
2. Check Database¦Verify every print 
3. Make sure Alias is exactly the same as the name of the report (I don't know why but on some reports, by simply changing the Alias to be the same as the name of the report would fix the problem) 
4. ASP code: use 
session("oRpt").DiscardSavedData 
and 
If IsObject(session("oPageEngine")) Then 
Set session("oPageEngine") = nothing 
End If 
set session("oPageEngine")=session("oRpt").PageEngine 
5. I tried to uninstall Crytal Report and reinstall the old version, but still have problem. I think there are some dll files which are placed somewhere else. 
6. I transferred reports to offsite server which has old version of CR7.0. They work, but numbers are displayed in form xx.00 instead of xx and the legend is "Sum of XXXXX" instead of just "XXXXX". 
7. I already convert database driver from PdsODBC.dll to PdsODBC.dll to make sure that the report uses the right dll file. 
 
Some other information: 
I use ODBC driver, stored procedure of MSSQL 7.0, and use ASP to call reports. However, all the reports work fine in Crystal Report Designer; the problem occurs only when I use ASP to call the report. 
 
Some tests: 
I make a new report which receive 4 parameters then call a stored procedure and then display them. The report works fine. 
-------------------------------------------------------- 
The stored procedure is: 
CREATE PROCEDURE TestSysPerf 
@CMinDate varchar(22), 
@CMaxDate varchar(22), 
@CStartShift varchar(22), 
@CEndShift varchar(22) 
AS 
 
DECLARE @MinDate DATETIME 
DECLARE @MaxDate DATETIME 
DECLARE @StartShift DATETIME 
DECLARE @EndShift DATETIME 
 
set nocount on 
 
SELECT @MinDate = Convert(datetime, @CMinDate) 
SELECT @MaxDate = Convert(datetime, @CMaxDate) + 1 
SELECT @StartShift = Convert(datetime, @CStartShift, 8) 
SELECT @EndShift = Convert(datetime, @CEndShift, 8) 
 
 
select 
@MinDate as MinDate, 
@MaxDate as MaxDate, 
@StartShift as StartShift, 
@EndShift as EndShift 
------------------------------------------------------ 
However, if I modify the existing report, which keeps using default parameters, to call the stored procedure above and all it does is display the parameters just like the new report does. This modified report still keeps using the default parameter. I deleted all the default parameters (set them to NULL), but somehow, the modified report still uses the default parameters. (ASP code does not change) 
 
Any suggestions? Anyone encounters this problem after installing the maintenance release 1? 
 
Thank you.

leszek · Sep 13, 1999

I used ADO connection but you can try refresh the report as below: 
Dim AnyName As YourReportName 
Dim AnyName1 As YourReorName1 ' and so on 
Dim MainRS As ADODB.Recordset 
 
'in place where you call for the report(s) 
Set AnyName = New YourReportName 
Set MainRS = Nothing 
 
MainRS.Open "SELECT * FROM sourcename" _ 
& "WHERE " _ 
& " AND " 
 
YourReportName.Database.SetDataSource MainRS 
CRViewer1.ReportSource = YourReportName 
 
This I used in VB6, the refresh stuff comes with Set = New 
I hope helps 
Leszek

phuctran · Sep 14, 1999

Thanhs, Leszek. In our ASP code, we already use 
 
session("oRpt").DiscardSavedData 
and 
If IsObject(session("oPageEngine")) Then 
Set session("oPageEngine") = nothing 
End If 
set session("oPageEngine")=session("oRpt").PageEngine 
 
which they told us that would refresh the parameters. But no hope :-(. We had to re-install the original version of SCR7.0. There are some guys, on other newsgroup, have the same bug like we do. I hope they will fix the bug soon. 
 
any suggestions? 
Thank you for your time, Leszek.

virgo · Sep 17, 1999

Your report makes me feel.... 
 
We have a major dll problem with Crystal. It uses as well as modifies some of the dlls that come with Windows. 
 
The year 2000 fix is dlls. 
 
We installed them. 
 
We have had problems ever since. Tech support says to install the maintenance release and that will fix the problems. 
 
Any information will be appreciated.

phuctran · Sep 17, 1999

... then Tech support says to install the MR2 to fix the bug of MR1 ... and so on

Actually, MR1 DOES fix some bugs like Exporting, Emailing, Running Report on the Web without interrupting each others. These are some fixed problems that I have known so far. But, in my opinion, data is gold. Therefore, we already re-install the orginal version of CR7.0 even though we will miss other features. (Who would buy a product which can do other things except reporting right data?) 
 
I dont' know what problem you have, but I think you should not install MR1. 
If you want to uninstall CR7.0, then this is the way we did. However, you should test it on your test server first. 
 
1. Uninstall CR7.0 from Start Menu -> Seagate Crystal Report -> Uninstall 
2. Delete folder C:\Windows\Crystal 
3. Delete folder C:\Program Files\Seagate Software 
4. Remove all files which has "CR" at the beginning of the filename, like crpe32.dll ... (move them into other directory, so that after you re-install Cr7.0 original you can check to see if you removed any extra files. 
5. Reinstall the original version of CR7.0 
 
Our reports work fine now after we did that. 
 
Hope it helps.

phuctran · Sep 17, 1999

On my first post, I said: 
3. Make sure Alias is exactly the same as the name of the report (I don't know why but on some reports, by simply changing the Alias to be the same as the name of the report would fix the problem) 
 
Please read it as: 
3. Make sure Alias is exactly the same as the name of the report (I don't know why but on some reports, by simply changing the Alias to be the same as the name of the *** STORED PROCEDURE *** would fix the problem) 
 
I just found out about that because usually the name of my report is named exactly as the name of the stored procedure it calls. 
 
Up to today, I fixed more than 50 reports by just doing that.

phuctran · Oct 6, 1999

bug found in MR1. Crystal Report said they will fix it soon (should say soooooooon)

phuctran · Nov 1, 1999

Bug found!!!!!!!! 
 
Parameters for SQL Stored Procedures through the CRPE are ignored. 
 
 
The information in the article refers to: 
Seagate Crystal Reports 7 
Applies to: 
Reported version only 
Maintenance Release 1 for Crystal Reports 7.0 
SQL 
Stored Procedure Parameters 
 
 
Synopsis 
 
Seagate Crystal Reports 7.0 Maintenance Release 1. 
 
Parameters passed to SQL Stored Procedures through the Crpe32.dll are being ignored or 
truncated and data is not returned from the stored procedure. The result is usually a blank report. 
 
Solution 
 
This behavior can be reproduced in a compiled report, through the Web Report Server and 
through the Automation Server. This behavior has been tracked as SCRTrack: #20857

Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

refresh parameters after installing maintenance release 1

phuctran

Programmer

leszek

Programmer

phuctran

Programmer

virgo

Programmer

phuctran

Programmer

phuctran

Programmer

phuctran

Programmer

phuctran

Programmer

Similar threads

Part and Inventory Search

Sponsor