My company is ready to contract an expert in working with ReportDocument/CrystalViewer in .Net at runtime; latest CR, latest .Net. I am one of the 2 proficient software developers who have been working on embedding it in to our core software product, we are 90+% there, but have been stuck on the rest too long.
Parameters have just been a nightmare. We have 3 functional scenarios as we bring a report to the viewer:
1. We know all parameter values, it is a 'system' report where the parameters are all under application control, and we want to supress the viewer from ever prompting/showing parameters
2. We have a starting set of parameter values determined in the application at runtime, use these values to do a 1st run of the report without prompting for parameters, then allow a user to subsequently prompt for parameters and re-run.
3. We don't have starting parameter values, prompt to the user before the report is ever run.
We just can't get it working right for all 3. We are also dealing with reports that have some very complex parameter types. Documentation is scarce, message boards are no longer a help, it probably requires advanced knowledge that would not be of any use to us once the project is done.