>When I was using the version of CR that was included with VB6 (4.x), I could code something like the following to pass parameters to the report based on MSSQL stored procedure:
>

>CRpt.ReportFileName = "c:\mediadna\listorders.rpt"
>CRpt.StoredProcParam(0) = gobjMailingOrder.MailingOrderID
>CRpt.StoredProcParam(1) = gobjMailingOrder.MailingTitle
>CRpt.StoredProcParam(2) = gobjClient.Clientname
>

>Now, StoredProcParam property doesn't seem to exist in the latest version (I'm using RDC) so how do I pass the values to the parameters?
>
>Also, if I design a CR report from within VB, it adds to the Designers folder in the Project Group but this report seems to be a different format than the report I design from within CR. The files have different file extensions, DSR/DSX vs. RPT respectively. Why and which way should I design my reports?
>
>TIA.

You have to use the parameterfields collection of the Report:

oReport.ParameterFields(0).AddCurrentValue( 'value here' )

BOb