Hi all,
We stumbled across another data point about this that doesn't mean a lot to us, but maybe it'll make someone else here go "Eureka!". (I hope I'm not hijacking your thread, Anina!) We discovered that there are actually two ways to fix Causes_a_Hang.rpt:
- [already known] Remove the Page N of M control(s).
- [new] Remove all references to Parameters within the report.
It's ok if there are Parameters defined in the report but unused, but the moment that a Parameter is connected to something, it causes the report to hang.
That said, we still can't see anything obviously different about Causes_a_Hang.rpt. In particular, we have various Works_Fine.rpt files that have both the Page N of M control as well as connected parameters. Just to reiterate our other weirdnesses:
- Causes_a_Hang.rpt works fine on CR9 in a VS2012 environment, CR9 in an installed environment, and CR13 in a VS2012 environment; it only breaks in a CR13 installed environment.
- Causes_a_Hang.rpt will work if Works_Fine.rpt is run first. (This is true even if we use Used_To_Cause_A_Hang.rpt as the Works_Fine report.)
I guess one additional thing worth mentioning is that the CR13 versions of all our reports differ from their CR9 counterparts in that the CR9 versions are "normal" reports, whereas CR13 use a single "hand-coded" Command table (which has the same SQL query as the CR9 version). Again, this is true of both Causes_a_Hang.rpt and Works_fine.rpt. (See http://scn.sap.com/thread/3297421.)
I'm sorry I still can't post examples of the two types of reports -- I know this is sorta asking the community to go at it blind. I guess what I'm wondering is whether there are any red flags that I should be looking out for. For example, we found an unrelated issue where VStudio borks the Selection Formula feature by autogenerating the line of code "crystalReportViewer.SelectionFormula = String.Empty;" in InitializeComponent()). Is it possible that VStudio is doing something similar with Parameters? Or do I have to something special to crystalReportViewer.ParameterFieldInfo? (What *is* crystalReportViewer.ParameterFieldInfo, anyway? Why does the Viewer have ParameterFields independent from the Report?)
As always, thanks for the help/time/effort,
Kevin