ASP.Net DS ->SSRS Report? ...or do I?

Is there a "native" way to pass a sorted table or dataset to a SSRS?
Or, is there another way to do the following...
I need to enable a minimum of 3 combo box drop downs to search by, a.k.a.
params.
These will use a sProc that executes some dynamic SQL to accomodate the
variations in params passed.
This is all good and working as a prototype in .Net.
However, most of the results sent to the browser also need to be sorted and then
hard copy printed, so...
Option One; Have the ASP.Net app do all .Net datalists and the like presenting
all the data as needed. Then when a user wishes to print that data they click
the printable version link, which would pass the current dataset as sorted to
SSRS, (my personal opinion is that this cannot be done with .Net and SSRS
alone.)
Option Two; Write my sorted data to a dynamic (rather than temp table) and then
call SSRS with params to get all the data as is from the dynamic table.
Option Three; give up, go home, take a nap, be a quiter, start crying like a
little boy, melt into a puddle of goo.
TIA
JeffP....I suggest rethinking a little how you do this. RS has a couple of ways to
integrate with your ASP. It has very good support for stored procedures. So
you can already use your stored procedure. You can integrate either by URL
or by web services. URL integration is the easiest way to go. Try just
creating a report with RS using the stored procedure and the parameters.
Once you have a report working then try out URL integration.
Passing a dataset is the hardest way to go to solve this. People have done
this but it requires a lot of jumping through hoops.
Bruce L-C
"JDP@.Work" <JPGMTNoSpam@.sbcglobal.net> wrote in message
news:e6eWkzObEHA.2340@.TK2MSFTNGP10.phx.gbl...
> Is there a "native" way to pass a sorted table or dataset to a SSRS?
> Or, is there another way to do the following...
> I need to enable a minimum of 3 combo box drop downs to search by, a.k.a.
> params.
> These will use a sProc that executes some dynamic SQL to accomodate the
> variations in params passed.
> This is all good and working as a prototype in .Net.
> However, most of the results sent to the browser also need to be sorted
and then
> hard copy printed, so...
> Option One; Have the ASP.Net app do all .Net datalists and the like
presenting
> all the data as needed. Then when a user wishes to print that data they
click
> the printable version link, which would pass the current dataset as sorted
to
> SSRS, (my personal opinion is that this cannot be done with .Net and SSRS
> alone.)
> Option Two; Write my sorted data to a dynamic (rather than temp table) and
then
> call SSRS with params to get all the data as is from the dynamic table.
> Option Three; give up, go home, take a nap, be a quiter, start crying like
a
> little boy, melt into a puddle of goo.
> TIA
> JeffP....
>|||Bruce,
I had a friend who is a much better programmer come over and we did a simple
sProc and created a SSRS Report.
We then ran the report as a SSRS report and then via URL; our biggest pain was
overcomming the "...you do not have permission to view this page..." or similar.
We added a default credential process if one was not present as well as a
user/pass textboxes w/cmd button to go to the report as a proof of concept that
we can accept win/auth, (won't be happening in any environment we have before
us) or default creds.
Anyway, back to my pain of displaying a report that was derived from the current
datalist control filtered and sorted as such.
I may try my dyna-temp table method. I think that there is a rumor indicating
that SSRS 05 will enable a method to call a SSRS report and pass it a .Net
DS/table.
I'd have thought that this would have been a first ed. feature(?)
TIA
JeffP...
"Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:ONp0KaPbEHA.3664@.TK2MSFTNGP12.phx.gbl...
> I suggest rethinking a little how you do this. RS has a couple of ways to
> integrate with your ASP. It has very good support for stored procedures. So
> you can already use your stored procedure. You can integrate either by URL
> or by web services. URL integration is the easiest way to go. Try just
> creating a report with RS using the stored procedure and the parameters.
> Once you have a report working then try out URL integration.
> Passing a dataset is the hardest way to go to solve this. People have done
> this but it requires a lot of jumping through hoops.
> Bruce L-C
> "JDP@.Work" <JPGMTNoSpam@.sbcglobal.net> wrote in message
> news:e6eWkzObEHA.2340@.TK2MSFTNGP10.phx.gbl...
> > Is there a "native" way to pass a sorted table or dataset to a SSRS?
> >
> > Or, is there another way to do the following...
> >
> > I need to enable a minimum of 3 combo box drop downs to search by, a.k.a.
> > params.
> >
> > These will use a sProc that executes some dynamic SQL to accomodate the
> > variations in params passed.
> >
> > This is all good and working as a prototype in .Net.
> >
> > However, most of the results sent to the browser also need to be sorted
> and then
> > hard copy printed, so...
> >
> > Option One; Have the ASP.Net app do all .Net datalists and the like
> presenting
> > all the data as needed. Then when a user wishes to print that data they
> click
> > the printable version link, which would pass the current dataset as sorted
> to
> > SSRS, (my personal opinion is that this cannot be done with .Net and SSRS
> > alone.)
> >
> > Option Two; Write my sorted data to a dynamic (rather than temp table) and
> then
> > call SSRS with params to get all the data as is from the dynamic table.
> >
> > Option Three; give up, go home, take a nap, be a quiter, start crying like
> a
> > little boy, melt into a puddle of goo.
> >
> > TIA
> >
> > JeffP....
> >
> >
>