After going through pain from yourself, here are a couple of pointers that hopefully save you time ...
Crystal Reports on MSDN - there's a lot to do.
Which approach to saving should be used with Crystal Reports - gives examples of details and code on how to best manage the life cycle of a report object
This post also provides some useful tips around the life cycle of a report object.
Deployment ... Crystal Reports do not run in the 64-bit environment, so when deploying to a 64-bit server, you will either have to configure IIS to run 32-bit mode or use the previous version of the runtime. I got lucky with the runtime that comes with VS2008, this can be found in
C: \ Program Files \ Microsoft SDK \ Windows \ v6.0A \ Bootstrapper \ Packages \ CrystalReports10_5
I note that you are using ASP.NET 2.0 - I am sure there is an equivalent VS2005 runtime. Try to run the deployment environment early in the project, as this will no doubt cause more headaches than you expect.
Finally, the last moment, which cost us time, is worth mentioning - the standard parameters screen in Crystal Reports will only take you so far. If you want to get complex information about how you present your parameters to the user (for example, having parameters that depend on the choice of another parameter), you will need to minimize your own parameter screens. This is fairly easy, since the object model gives you access to all the information you need about the parameters. We took the path of creating a screen of general parameters, which is built in accordance with the parameters found in the report to which it points.
Paul nearney
source share