Local reports with ADO.NET Dataset help

I'm trying to use a local report in a Windows Forms application that
uses an ado.net dataset. The trouble is that I'm trying to figure out
how to access data within related tables. If the dataset has a table
called Customers with two records in it, how do I go about displaying
the data from a particular customer in a particular place? Can I choose
the row to show based upon a key in a separate table? That would be
ideal. Any ideas? I've searched and found no answers.
Thanks,
BrianHi Brian, I'm running with the same problem.
For some reason all I see it's one of the DataTable's data...
have you figured this out yet?
Best regards,
Sebasti=E1n
On Oct 26, 8:18 pm, Brian Vallelunga <brian.vallelu...@.gmail.com>
wrote:
> I'm trying to use alocalreport in a Windows Forms application that
> uses an ado.netdataset. The trouble is that I'm trying to figure out
> how to access data within related tables. If the dataset has a table
> called Customers with two records in it, how do I go about displaying
> the data from a particular customer in a particular place? Can I choose
> the row to show based upon a key in a separate table? That would be
> ideal. Any ideas? I've searched and found no answers.
> > Thanks,
> > Brian|||I started to look into local reports and decided it was a pain for this very
reason. However, I do know what you need to do conceptually. Nothing has
changed as far as how to solve the problem in the design of the reports. A
server report can be turned into a local report (you just rename the rdl
file to rdlc). Indeed, my suggestion on how to develop is to develop inside
the report designer (even if no server you can design and preview). Then
once working bring it into you app.
Now, in RS the way you handle master detail is by sub reports. That has not
changed. For local reports you have to do the same thing. You have to tie
into an event in the sub report to take the parameter and give the sub
report the appropriate data. So, let's say that you have a dataset all
populated. The main report is tied to the data table for the master. Then
you have the sub report and you tie the subreport parameter to a field of
the master table record. In the event you then would need to filter the
appropriate data table and set the source of the subreport to that. Note
that this event will be called for each record in the master.
Hope this helps at least conceptually on what you need to do.
After seeing all the hoops I would have to go through, I decided to stay
with server based reports.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<sebastiangomezcorrea@.gmail.com> wrote in message
news:1162385028.994774.52040@.k70g2000cwa.googlegroups.com...
Hi Brian, I'm running with the same problem.
For some reason all I see it's one of the DataTable's data...
have you figured this out yet?
Best regards,
Sebastián
On Oct 26, 8:18 pm, Brian Vallelunga <brian.vallelu...@.gmail.com>
wrote:
> I'm trying to use alocalreport in a Windows Forms application that
> uses an ado.netdataset. The trouble is that I'm trying to figure out
> how to access data within related tables. If the dataset has a table
> called Customers with two records in it, how do I go about displaying
> the data from a particular customer in a particular place? Can I choose
> the row to show based upon a key in a separate table? That would be
> ideal. Any ideas? I've searched and found no answers.
> Thanks,
> Brian|||Hey Bruce, thanks for the reply.
Even though I'm working with local reports, I have to ask... how do you
do what I'm trying with rdl reports? Is there some kind of wizzard or
something?
TIA
On Nov 1, 12:08 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> I started to look into local reports and decided it was a pain for this v=ery
> reason. However, I do know what you need to do conceptually. Nothing has
> changed as far as how to solve the problem in the design of the reports. A
> server report can be turned into a local report (you just rename the rdl
> file to rdlc). Indeed, my suggestion on how to develop is to develop insi=de
> the report designer (even if no server you can design and preview). Then
> once working bring it into you app.
> Now, in RS the way you handle master detail is by sub reports. That has n=ot
> changed. For local reports you have to do the same thing. You have to tie
> into an event in the sub report to take the parameter and give the sub
> report the appropriate data. So, let's say that you have a dataset all
> populated. The main report is tied to the data table for the master. Then
> you have the sub report and you tie the subreport parameter to a field of
> the master table record. In the event you then would need to filter the
> appropriate data table and set the source of the subreport to that. Note
> that this event will be called for each record in the master.
> Hope this helps at least conceptually on what you need to do.
> After seeing all the hoops I would have to go through, I decided to stay
> with server based reports.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <sebastiangomezcor...@.gmail.com> wrote in messagenews:1162385028.994774.5=2040@.k70g2000cwa.googlegroups.com...
> Hi Brian, I'm running with the same problem.
> For some reason all I see it's one of the DataTable's data...
> have you figured this out yet?
> Best regards,
> Sebasti=E1n
> On Oct 26, 8:18 pm, Brian Vallelunga <brian.vallelu...@.gmail.com>
> wrote:
>
> > I'm trying to use alocalreport in a Windows Forms application that
> > uses an ado.netdataset. The trouble is that I'm trying to figure out
> > how to access data within related tables. If the dataset has a table
> > called Customers with two records in it, how do I go about displaying
> > the data from a particular customer in a particular place? Can I choose
> > the row to show based upon a key in a separate table? That would be
> > ideal. Any ideas? I've searched and found no answers.
> > > Thanks,
> > > Brian- Hide quoted text -- Show quoted text -