This is one of the reasons that I tell people that local mode is not a
panacea. You have to have code that responds to the appropriate event. You
can do supreports in local mode but it is definitely more work. I was
exploring local reports (I use the winform control) and then I realized it
was going to be a pain and since I had the server around anyway, I decided
to abandon using local mode. The benefits in my situation did not justify
the extra complexity and effort.
I suggest posting a new question about subreport in local mode. Do it both
here and the MSDN forums (more, much more, Microsoft presense is in the
forums).
So, other than telling you it is possible and at one point I at least
conceptually saw how to do subreports in local mode, I cannot be much help
to you.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
[quoted text, click to view] "Christian Nein" <no@spam.com> wrote in message
news:%23ryU1Q9qGHA.4100@TK2MSFTNGP02.phx.gbl...
> Hi Bruce,
>
> thank you for answering. The reports that I have to design have to be
> printed out so I can't use drill through reports. Thus, if I got you
> right, I will have to use a subreport, in particular as I want to use 2
> datasets und not put all the data into one table (which still would be my
> emergency solution), is that correct?
>
> I am using RDLC-reports which I display in a ReportViewer control located
> on a form. When loading the form, I pass the name of the rdlc-file to
> display and a dataset containing the data to be displayed. So the
> ReportViewer control loads the report and binds the passed dataset to it.
> If I used a subreport I would also have to bind the data to the nested
> subreport. This is where got in trouble: I found no way to access the
> nested subreport to bind the data to it. Can you tell how I can assign the
> passed data to the nested subreport?
>
> Regards
> Christian
>
>
>
> "Bruce L-C [MVP]"
>> For what you want to do (1 - Many) subreports are the way to go. From a
>> design perspective you might also want to consider looking a drill
>> through reports. These are very easy to design in RS.
>>
>> "Christian Nein" <nospam@nospam.de> wrote in message
>> news:uzLpB62qGHA.4960@TK2MSFTNGP04.phx.gbl...
>>> Hi,
>>>
>>> I have a report containing 2 datasets:
>>> - dataset 1 containing ProductGroups
>>> - dataset 2 containing the Articels contained in the ProductGroups
>>> Both datasets are 1:N-related by the ProductGroupID (1 product group
>>> contains N articles)
>>>
>>> I want to display each product group with a list of the contained
>>> articles.
>>> In MS Access I was used to use subreports to display 1:N-related data
>>> (in this case that would mean creating a subreport for the articles).
>>> But I have read that in reporting services, subreports have some
>>> drawbacks concering performance and that it is recommended to use
>>> multiple data regions. I tried to use a List element instead and put a
>>> table for displaying the detal data on it. But by problem is that the
>>> data comes from two datasets and a List is always bound to one dataset.
>>> (Anyway, in my case the subreport has some additional drawbacks, because
>>> I use the ReportViewer control to display the report and bind the
>>> datasources dynamically while displaying. At this point I have no
>>> possibility to access the subreport to bind it to its datasource)
>>>
>>> My question ist: do I relly have to store all the data in ONE dataset
>>> (which will be the dataset for the List) and group it by the
>>> ProductGroupID or is there another way to get the functionality of
>>> subreports, maybe by the usage of nested lists? I have the book
>>> "Professional SQL Server 2005 Reporting Services" but I have found no
>>> solution for my problem there.
>>>
>>> Thanks in advance for any support and best regards
>>> Christian
>>>
>>
>>
>
>