2024 Apr 03 11:18 AM - edited 2024 Apr 03 12:38 PM
We use Crystal Report Viewer 13 SP34 (32-Bit) in a .NET application.
When printing from preview the custom page range does not behave as expected:
Selected Page Range | Result |
any single page value (e.g. 3) | page currently shown in preview window |
single page range (e.g. 3-3) | page currently shown in preview window |
comma-separated selection (e.g. 1,2) | error message "something went wrong" |
combined selection (e.g. 1-2,3) | error message "something went wrong" |
page range selection (e.g. 1-2) | prints range as expected |
Can anyone confirm this problem and is there a solution?
Request clarification before answering.
You are welcome...
The P2P API is a legacy mode designed when CR for VS was installed with Visual Studio back in VS6 days.
It's normal behaviour in what is called CR Basic, same as the Embedded report designer, has limited functionality, it uses the printer saved in the Report. You can test this by opening the report in CRD and hit the Print button, select the Printer and save the report. Next time your app should default to that selected printer.
Also the Viewers default printer API is P2P, using the routines in my test app uses the PrintOutputController (POC) and allows your users to select the printer of choice.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
78 | |
30 | |
10 | |
8 | |
8 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.