Main/Sub Report Passing Parameter

Question

This is a twist on the general passing parameter question:
1. The main report is a detail report based on a stored procedure.
2. The sub report is also based on a stored procedure. This SP calculates the values that will be introduced into a 'table' drawn on the report canvas. The SP consists of a CTE which is a 'reduced' version of the Detail SP used in the main report - to ensure that all the same records are being retrieved between the main and sub reports. Another select, following the CTE, sums the values and makes them available to the Sub Report.
The client has requested the availability to view records where an Activity Date falls within the last full week, the last month, this month, and YTD. The report is available both through Infoview as well as a scheduled version. The client wants to make a selection as to time period through Infoview.
Most other users will be using a printed copy of the 'general' report.
I thought to use the SAVED DATA in SELECTION REPORTS and use Crystal functions to handle this. The SAVED DATA and an optional parameter allowed the user (in Infoview) to change the parameters. This works fine in the main report.
HOWEVER, the sub report needs to update the totals for the groups of properties that are aggregated in the sub report's summary Stored Procedure. Since the time range will, on changing in the Main Report, reflect different counts,  I need to be able to tell the sub report what the main report is doing.
The Main report has an Optional Parm ({?Account Open}) which allows the selection of a data range
The SAVED DATA selection uses the values from the parm:
if not hasvalue({?Account Open}) then 1=1
    else if hasvalue({?Account Open}) and {?Account Open}=0 then 1=1
    else if hasvalue({?Account Open}) and {?Account Open}=1 then {Account_open_date_newest}in LastFullWeek
    else if hasvalue({?Account Open}) and {?Account Open}=2 then {Account_open_date_newest}in LastFullMonth
    else if hasvalue({?Account Open}) and {?Account Open}=3 then {Account_open_date_newest}in Yeartodate
    else if hasvalue({?Account Open}) and {?Account Open}=4 then {Account_open_date_newest}in CDateTime (CurrentDate-(DayOfWeek(CurrentDate)+1),CTime(00,00,00)) to CDateTime (CurrentDate+(7-(DayOfWeek(CurrentDate))),CTime(23,59,59))
    else 1=0;
My problem in passing the optional param selection made by the user down to the sub report in order to update the counts.
Any help would be gratefully appreciated! I have included a snap of the Table from tyhe subreport and a snap of the optional parm from the Main Report

Answer 1

Jamie -
Thank you for your reply. I've spent the morning working on the two directions you had provided me with.
Cross tabs: I took one report, created a cross tab for it, and, as expected, it worked as desired. The issue I'm having is where to place it on the report canvas. If I'm correct, the only place where it can be placed is in a header or footer - the sub report is currently residing in Page Header D (there's a lot of suppression and reveals in these reports). The cross tab does not want to be placed there. It's currently living in the Report Header... further, the cross tab occupies page 1; the remainder of the report starts on page two. Not what needs to happen. The current business specification for the report is: Page 1 includes a page header which includes (through iterations a-e) logo, print date info, the sub report showing the summary a series of group headers which in effect creates an index into the various business units. By clicking on a business unit, any groups under it are exposed. By clicking on the sub group, customer data is exposed. As you go to the 'next page', the Summary sub-report is eliminated and the groups under the Business Unit are shown. All of these dynamics are based on section suppression and unhiding based on the user's interaction, which why the placement of the Summary data is important. If you have any hints on managing the cross tab and its placement, I would be eager to hear them.... (btw - the number of rows in the cross-tab can range from 0 to 12. That dynamism is not a problem with the sub report - would it be for the cross tab?)
Parameter Passing: I took one of the reports and (1) ensured that the sub report had the exact  same parameter (called Account Open) as the Main Report. (2) ensured that the Saved Data filters in both reports were the same. (In order to do that I had to update the stored proc for the sub report to include an account date field). (3) I then went to link the two reports selecting the Account Open parameter in both the containing and the Fields to Link To list boxes (see the graphic LINK.JOG. This produced no useful result - the Summary showed ALL records- the container report properly showed the count for last full month (see SUMMARY.JPG) (4) I then tried to link a field from the sub report to the Parameter, but only 4 of the six fields from the stored proc's select were displayed. (Prior to this Select there is a CTE which collects the data with a ROW OVER.. PARTITION function):
SELECT
customer_business_unit_name,
account_open_date_newest,
sum (CASE WHEN currentrisk =1 THEN 1 Else 0 End) lowcount ,
sum (CASE WHEN currentrisk =2  THEN 1 Else 0 End) midcount ,
sum (CASE WHEN currentrisk =3 THEN 1 Else 0 End) highcount,
sum (CASE WHEN currentrisk =0 THEN 1 Else 0 End) unknown
FROM    records
WHERE   rn = 1
group by customer_business_unit_name,account_open_date_newest
Only the COUNT fields show up in the Fields box (see the graphic LINKS CHECKED.JPG).
Where have I gone wrong??
Again, thank you for your earlier reply.