Symptoms

Report Commander is only able to set parameters that are defined for the main report. If a subreport has parameters that are not linked to the main report, they cannot be set using Report Commander. When you try to run the report in Report Commander, a Crystal Reports window appears, prompting you for the missing parameters.

Cause

Report Commander uses software components provided by Business Objects (the makers of Crystal Reports). Due to limitations in these components, Report Commander does not have access to these parameters.

Workaround

This problem only applies to parameters that appear in the subreport and are not linked to the main report. To avoid the problem, create a new parameter of the same type in the main report, and then link it to the parameter in the subreport. Report Commander will allow you to set the parameter in the main report, and its value will be passed to the subreport.

For example, your main report has a "CustomerID" parameter. The report has a subreport that has two parameters: "CustomerID" and "OrderID". The "CustomerID" parameter is used to link the main report and the subreport.

When you run this report from the Crystal Reports designer, you are prompted for both the CustomerID and OrderID parameters. When you view the report in the Report Commander Command Line Builder, only the CustomerID is displayed. If you run the report using the Report Commander command line, Crystal Reports prompts you for the OrderID.

To resolve the problem, add an OrderID parameter to the main report, and change the subreport linking so that both the CustomerID and OrderID parameters are used to link the two reports.

Report Commander will now prompt for both the CustomerID and OrderID parameters, and the report will run successfully in Report Commander.