cancel
Showing results for 
Search instead for 
Did you mean: 

Changing CrystalViewer ID causes 'Next Page' to not work

Former Member
0 Kudos

Development environment: Windows 8, Visual Studio 2013, ASP.Net web development environment, 64bit machine. CR 13_0_10 installed.

Also, deploying to a test environment of Windows Server Web edition (c) 2007 SP1 32 bit

Problem occurs in development and test environment.


First of all I guess we need to clarify that what we are trying to do is valid;


We are displaying a few CR's in our website using schemas for the data source and passing associated XMLs at runtime to the CR.

We want to rename the Crystal Report that is downloaded to a users machine if they click the 'Export' button, so that every report is not called CrystalViewer1 (the ID of the CR control).

We have just started trying this by renaming the ID of the Crystal Viewer to whatever we want.

What happens is that the Crystal Viewer comes up and displays the first page, but on going to the next page we have the following error occur and the page looks like it's hanging, with the Crystal progress circle animation.

Taking out the code that renames the ID stops the error from happening.

Example code that breaks it:

CrystalReportViewer1.ID = "JiminyCricket"

Have also tried setting the SummaryInfo.ReportTitle of the ReportClass, but to no avail.

Is what we are doing valid? And if not, how else should we be doing it?

Many thanks for your time,

Julian Tucker

Accepted Solutions (1)

Accepted Solutions (1)

former_member183750
Active Contributor
0 Kudos

Hi Julian

Not sure what the error is as it was not included, but I suspect it is this:

f that is the case place your code at page init:

Private Sub WebForm1_Init(sender As Object, e As System.EventArgs) Handles Me.Init
    CrystalReportViewer1.ID = "test"
    CrystalReportViewer1.ReportSource = "c:\tests\formulas.rpt"
End Sub

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

  Follow us on Twitter

Former Member
0 Kudos

Ludek,

Spot on. Worked first time. Thank you very much. And yes, sorry, that was the error.

Julian

former_member183750
Active Contributor
0 Kudos

Happy it's working and many thanks for letting us know the issue is resolved.

Have a great weekend

- Ludek

Answers (0)