I think you should look at using subreports. I don't have a complete handle
on what you are doing. Subreports are how you join disparate data like this.
It could be that the parent data you will need to add (but not display) the
data that you will need to pass on to the subreport as a parameter.

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
I don't think subreports is the right approach. I will try and explain
my problem more clearly.
Employees enter their time against a cost category/project
combination. It is easy to display this data in a table.
However, the complicating issue is that there is also budgetary data
associated with the cost category/project combination. This budget to
cost category/project relationship is a one-to-one relationship and
only exists at the cost category level (not the employee level)
whereas the employee to cost category/project relationship is one-to-
many.
In case that is not clear, the data structure is as follows
Project
Cost Category (Time Budgeted)
Employee (Time Worked)
I currently have a data set where all of the budget and time data is
summed up at the cost category/project in the query so that it looks
as follows:
Project Cost Category Hours Worked Hours Budgeted
The data set involving the employees is as follows:
Employee Project Cost Category Hours Worked
As you can see, the second data set includes another level of data and
I cannot figure out how to combine the two into a report that should
look something like this:
Project
Hours Worked Hours Budgeted
Cost Category
22.5 20.0
Employee A 10.0
Employee B 12.5
Any help would be appreciated. Thanks.
On Jul 9, 3:52 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@hotmail.com>
wrote:
> I think you should look at using subreports. I don't have a complete handle
> on what you are doing. Subreports are how you join disparate data like this.
[quoted text clipped - 29 lines]
>
> - Show quoted text -
Bruce L-C [MVP] - 14 Jul 2008 18:26 GMT
This still seems to me to be a subreport solution. Subreports are just
regular reports that have parameters. You develop the report by itself and
test it then you embed it and link the parameters to whatever should be used
for the parameter values. It loosk to me that your
Project Cost Category Hours Worked Hours Budgeted
is the main report. The
Employee Project Cost Category Hours Worked
is the subreport. The subreport has two parameters: Project and Cost
Category.
This seems to be the classic master detail type of report which is exactly
what subreports are used for.

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
I don't think subreports is the right approach. I will try and explain
my problem more clearly.
Employees enter their time against a cost category/project
combination. It is easy to display this data in a table.
However, the complicating issue is that there is also budgetary data
associated with the cost category/project combination. This budget to
cost category/project relationship is a one-to-one relationship and
only exists at the cost category level (not the employee level)
whereas the employee to cost category/project relationship is one-to-
many.
In case that is not clear, the data structure is as follows
Project
Cost Category (Time Budgeted)
Employee (Time Worked)
I currently have a data set where all of the budget and time data is
summed up at the cost category/project in the query so that it looks
as follows:
Project Cost Category Hours Worked Hours Budgeted
The data set involving the employees is as follows:
Employee Project Cost Category Hours Worked
As you can see, the second data set includes another level of data and
I cannot figure out how to combine the two into a report that should
look something like this:
Project
Hours Worked Hours Budgeted
Cost Category
22.5 20.0
Employee A 10.0
Employee B 12.5
Any help would be appreciated. Thanks.
On Jul 9, 3:52 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@hotmail.com>
wrote:
> I think you should look at using subreports. I don't have a complete
> handle
[quoted text clipped - 32 lines]
>
> - Show quoted text -