cancel
Showing results for 
Search instead for 
Did you mean: 

parameters page pops up after running report successfully

0 Kudos

Recently our team decided to move from Win7 to Win10 on the development side of our C# projects.

Now all projects are using Visual Studio 2022, Crystal Report 13.0.4000.0, Microsoft SQL Server 2020, Win10

On the production side, we are using SQL server 2018, Azure version 1.25.1(system setup), Windows server 2012 R2, and the same version of Crystal Report.

All reports work fine, they are running with different parameters that users can fill out on websites.

In some reports, users are able to export them and move between pages(most of them have only one record with 1 page to 8 pages of results)

But on some reports(most of them have more than one record), users are not able to export them, if users want to go to the next page, the parameters page pops up and it has to be filled out again, then users can export it, and moving between pages works fine. (attached file: popupmessageCR)

Most of these reports are produced with a combination of views and tables as their data sets.

We did a lot of research and read most of the related articles, but none of the solutions worked. Check DLL references, save reports in new projects, order program code, and ensure that the folder exists win64_x64 and win32_x64 etc.

Our stakeholders are in their peak season work and we asked them to enter the values of these parameters again so that they can export and move between pages.

We need help to solve the issue.

Accepted Solutions (1)

Accepted Solutions (1)

DonWilliams
Active Contributor
0 Kudos

It could be an issue with MS SQL 2020, currently not supported, see the platform PDF for more info:

https://www.sap.com/documents/2016/06/f871031e-757c-0010-82c7-eda71af511fa.html

You could try using the MS ODBC client 17 or 18, you will need to open each report and set the logon info to one of those Clients. CR won't "fix" it on the fly, you need to manually update each report.

Windows 7 was likely using a very old MS Client which CR no longer supports so to "fix" the report the only way is to manually update each one, CR keeps track of the Client DLL used in the RPT file. It is likely failing because it can't find the old client. And the SQL generated is not compliant with 2020.

Answers (5)

Answers (5)

0 Kudos

We found that only reports that have date/time parameters faced this issue, by changing date/time parameters to string inside the report and sending string value, the problem was resolved.

Win 10

Visual Studio 2022

SQL Server 19.1

Crystal Report 13.0.4000.0

DonWilliams
Active Contributor
0 Kudos

You also need to use Sessions and Postback methods to keep the report in scope, next page, exporting or printing will cause the report to refresh so you need to keep the report in scope.

See this KBA on using them:

https://userapps.support.sap.com/sap/support/knowledge/en/1985571

Also, the 13.0.4000.0 is the framework version, go to Programs and Feature to see the actual SP number.

SP 34 is the latest and you can get it from here:

https://help.sap.com/docs/SUPPORT_CONTENT/crystalreports/3354091173.html

0 Kudos

Thanks, Don.

The latest version was installed from the SAP website, all reporting parameters(int, string) work with this implementation and session keeps the data except for the date/time parameters.

ido_millet
Active Contributor
0 Kudos

Does the report contain subreports?

Can you attach the rpt file (change extension to .txt to allow the attachment)?

0 Kudos

Thanks, Ido. Please check the attached file. "ParticipantAddressslist" is one of the reports that has 2 date parameters and the parameters page pops up after running the report.participantaddresslist.txt

ido_millet
Active Contributor
0 Kudos

No subreports so that suspect is out.
You didn't say if you are running the report using a web application.
If you do, follow Don's suggestions.

0 Kudos

No, it doesn't have subreport

0 Kudos

saperror2.png

Parameter page after running report and users wanted to go to the next page.

DellSC
Active Contributor
0 Kudos

This is happening because you need to make some updates to your code to work with the newer version of the SDK. Please see this blog for information about the updates you need to make.

-Dell

0 Kudos

Thanks, Dell.

We applied all the required changes and most of the reports are working on our system, The parameters message pops up only for the reports that have Date parameters and asks users to input them again, this is a common thing between them. Any ideas or advice on this?saperror.png