Problem to solve:
Build a query on the fly, add the returning DataSet to the CrystalViewer::ReportSource on runtime and allow the toolbar or treeview to navigate the pages.
Symptoms:
The report is created as expected BUT the toolbar/treeview don't work at all. If I press the treeview or toolbar, I get a post back and then different errors.
Q1: Do I need to handle the events at the server (if yes why bother with the built-in Toolbar/Treeview)?
Q2: Is there any special settings to add in the report file (.rpt) to enable navigation?
I am discouraged with the documentation: 20+ pages on architecture and 2 lines with the signatures for the toolbar/treeview methods(the features that I required)...
Build a query on the fly, add the returning DataSet to the CrystalViewer::ReportSource on runtime and allow the toolbar or treeview to navigate the pages.
Symptoms:
The report is created as expected BUT the toolbar/treeview don't work at all. If I press the treeview or toolbar, I get a post back and then different errors.
Q1: Do I need to handle the events at the server (if yes why bother with the built-in Toolbar/Treeview)?
Q2: Is there any special settings to add in the report file (.rpt) to enable navigation?
I am discouraged with the documentation: 20+ pages on architecture and 2 lines with the signatures for the toolbar/treeview methods(the features that I required)...
