Hi all,<br>
<br>
I have around 150 reports and they worked fine before I installed Crystal Report Maintenance Release 1 on Aug, 99. <br>
<br>
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.<br>
<br>
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.<br>
<br>
This is what I have done so far:<br>
1. Uncheck File¦"Save report with data"<br>
2. Check Database¦Verify every print<br>
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)<br>
4. ASP code: use<br>
session("oRpt").DiscardSavedData<br>
and<br>
If IsObject(session("oPageEngine")) Then<br>
Set session("oPageEngine") = nothing<br>
End If<br>
set session("oPageEngine")=session("oRpt").PageEngine<br>
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.<br>
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".<br>
7. I already convert database driver from PdsODBC.dll to PdsODBC.dll to make sure that the report uses the right dll file.<br>
<br>
Some other information:<br>
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.<br>
<br>
Some tests:<br>
I make a new report which receive 4 parameters then call a stored procedure and then display them. The report works fine.<br>
--------------------------------------------------------<br>
The stored procedure is:<br>
CREATE PROCEDURE TestSysPerf<br>
@CMinDate varchar(22),<br>
@CMaxDate varchar(22),<br>
@CStartShift varchar(22),<br>
@CEndShift varchar(22)<br>
AS<br>
<br>
DECLARE @MinDate DATETIME<br>
DECLARE @MaxDate DATETIME<br>
DECLARE @StartShift DATETIME<br>
DECLARE @EndShift DATETIME<br>
<br>
set nocount on<br>
<br>
SELECT @MinDate = Convert(datetime, @CMinDate)<br>
SELECT @MaxDate = Convert(datetime, @CMaxDate) + 1<br>
SELECT @StartShift = Convert(datetime, @CStartShift, 8)<br>
SELECT @EndShift = Convert(datetime, @CEndShift, 8)<br>
<br>
<br>
select<br>
@MinDate as MinDate,<br>
@MaxDate as MaxDate,<br>
@StartShift as StartShift,<br>
@EndShift as EndShift<br>
------------------------------------------------------<br>
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)<br>
<br>
Any suggestions? Anyone encounters this problem after installing the maintenance release 1?<br>
<br>
Thank you.<br>
<br>
<br>
<br>
<br>
<br>
I have around 150 reports and they worked fine before I installed Crystal Report Maintenance Release 1 on Aug, 99. <br>
<br>
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.<br>
<br>
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.<br>
<br>
This is what I have done so far:<br>
1. Uncheck File¦"Save report with data"<br>
2. Check Database¦Verify every print<br>
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)<br>
4. ASP code: use<br>
session("oRpt").DiscardSavedData<br>
and<br>
If IsObject(session("oPageEngine")) Then<br>
Set session("oPageEngine") = nothing<br>
End If<br>
set session("oPageEngine")=session("oRpt").PageEngine<br>
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.<br>
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".<br>
7. I already convert database driver from PdsODBC.dll to PdsODBC.dll to make sure that the report uses the right dll file.<br>
<br>
Some other information:<br>
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.<br>
<br>
Some tests:<br>
I make a new report which receive 4 parameters then call a stored procedure and then display them. The report works fine.<br>
--------------------------------------------------------<br>
The stored procedure is:<br>
CREATE PROCEDURE TestSysPerf<br>
@CMinDate varchar(22),<br>
@CMaxDate varchar(22),<br>
@CStartShift varchar(22),<br>
@CEndShift varchar(22)<br>
AS<br>
<br>
DECLARE @MinDate DATETIME<br>
DECLARE @MaxDate DATETIME<br>
DECLARE @StartShift DATETIME<br>
DECLARE @EndShift DATETIME<br>
<br>
set nocount on<br>
<br>
SELECT @MinDate = Convert(datetime, @CMinDate)<br>
SELECT @MaxDate = Convert(datetime, @CMaxDate) + 1<br>
SELECT @StartShift = Convert(datetime, @CStartShift, 8)<br>
SELECT @EndShift = Convert(datetime, @CEndShift, 8)<br>
<br>
<br>
select<br>
@MinDate as MinDate,<br>
@MaxDate as MaxDate,<br>
@StartShift as StartShift,<br>
@EndShift as EndShift<br>
------------------------------------------------------<br>
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)<br>
<br>
Any suggestions? Anyone encounters this problem after installing the maintenance release 1?<br>
<br>
Thank you.<br>
<br>
<br>
<br>
<br>