Symptoms
After updating to Report Commander version 2.2, reports that previously worked correctly now produce the following error from Report Commander:
This occurs only when your command line does not specify values for all parameters in the report, and when the missing parameters are not designated as optional.
Cause
A fix was made in version 2.2 to correct a similar problem (see article K00000513). However, this fix causes problems for the case described above, because Report Commander attempts to tell Crystal Reports that the parameter value is unspecified, but the report does not allow the value to be missing. In previous versions, Report Commander skipped the parameter entirely, and Crystal Reports treated it as an empty string ("") rather than as a missing (null) value.
Workaround
Modify your command line to specify empty values ("") for any missing string parameters, or modify the report to designate the parameter as optional.
Status
Report Commander 2
This issue has been resolved. Resolved in version 2.3.
