Group Tree issue, web form vs Win form?

Question

Using Crystal Reports for Visual Studio 2010...
I am using the same report file for a Win form and web form version of the same utility program.  The report was built bases on a view to the database, and both programs populate the report based on a dataset which has the same columns with restrictive where clauses, based on user input prior to populating the report.
On the Win Form version, when the user clicks a group on the Group Tree, the report nicely navigates to the appropriate section of the report. However... on the Web version, the ReportViewer makes a return trip to the database, refreshing the data with the entire view, overwriting the original content.  In other words, out of lets say 50,000 possible records, if I ask for 50, they are displayed as I want, but in the web report, if I try and navigate to any of the 50, I get all 50,000 (an no navigation), an unwanted return to the database.
I am perplexed, as it is the same report file used by both versions.
I tried hiding the Group Tree panel (I don't need it), per instructions (CrystalReportViewer1.ToolPanelView = ToolPanelViewType.None;)
But that only closes the panel, and it is still available to the user to open (icon remaining). Is it possible to really make the Group Tree unavailable?
thanks,
Mark

Answer 1

Ludek,
What I wish to do is follow the instructions for placing the report in a session, per your suggestions above:
     Place the report in session. See
     KBA 1985571 - How to use sessions in web applications using the Crystal Reports viewer (the complete code)
OK, since I'm new at this, where does the code go? I can't seem to resolve RAPPBasePage, and I admit that without more specific directions on the linked page, I'm more than a bit lost with this.
Thanks,
Mark
Below is a complete code that describes how to ensure the report is in
session:
public partial class Reports : RAPPBasePage
      private ReportDocument crReportDocument;
      protected override void Page_Init(object sender, EventArgs e)
           //connect method to master event
           base.Page_Init(sender, e);