Using Multiple Datasets from a single Stored Procedure

[Kirk]

I have a pretty simple stored procedure that is used to generate my
report data. There is a single passed parameter (the record ID) and
the SP returns TWO datasets. For the sake of discussion here, lets
say they are "header" and "detail" information about the passed ID.

How can I use both of these DataSets on the same report, preferably,
without having to use subreports? I can temporarily remark out the
code that generates the first "header" dataset, and create a new
"details" dataset in my report based on this. However, when I do this
(and un-comment the code before running it), the report shows nothing
for the second "details" data set.

I can see a couple of options, neither of which is prefered by me.
First, I could create another stored procedure and have two that
basically do the same thing (which is a maintenance headache).
Second, I could create a subreport (which make the report somewhat
more complicated).

I would appreciate any suggestions of how to handle this, or any
feedback on the above. Thank you!

[Anil Sharma]

Kirk,

You can use more than 1 data-set in the same report, preferable you
are not using two data-sets in the same table / matrix.

so, please elaborate, where and for what purpose 2 data-sets is
required.

Thanks,
Anil

Post by Kirk
I have a pretty simple stored procedure that is used to generate my
report data.  There is a single passed parameter (the record ID) and
the SP returns TWO datasets.  For the sake of discussion here, lets
say they are "header" and "detail" information about the passed ID.
How can I use both of these DataSets on the same report, preferably,
without having to use subreports?  I can temporarily remark out the
code that generates the first "header" dataset, and create a new
"details" dataset in my report based on this.  However, when I do this
(and un-comment the code before running it), the report shows nothing
for the second "details" data set.
I can see a couple of options, neither of which is prefered by me.
First, I could create another stored procedure and have two that
basically do the same thing (which is a maintenance headache).
Second, I could create a subreport (which make the report somewhat
more complicated).
I would appreciate any suggestions of how to handle this, or any
feedback on the above.  Thank you!