Re: Stored Procedure parameter (@Carrier) used in report and can't be set via code

In short, I believe the stored procedure's parameters that are defined in the rpt file are completely ignored and the values are not passed into the report since Crystal doesn't actually execute the stored procedure itself.  Does that seem reasonable?  Any way around that?

Thanks.