I think we had something like that happen, but you won't like the solution...we did away with the Crystal parameter screens. Our ERP system collects the information for the parameters, calls the stored proc and sets the resulting dataset to the reports dataset, and then we display the report.
In the long run, it has been really nice, there is only 1 data table, so there is only 1 call to the database. If there is a subreport (and the usually isn't), it is looking in the same table, so it is all in memory and no additional calls to the database. The parameter inputs can look way nicer and have much more functionality and ease of use for the users.
It kind of sounds like the report is getting parameters to populate the stored procs that populate the parameters, but Crystal is odd when it comes to populating Command objects for parameters...at least every now and then.
IP Logged
