It's going to be too long, in order to get Reporting Services, website and
all installed here, so I'm looking for another way to get a few reports into
production
The reports are already done in SSRS - so I figured I could just, somehow,
'port' them over to our existing ASP.Net website, and use the ReportViewer
control
However, I've never done this, and it looks like it's not going to be as
simple as I thought. I gather this, especially since I have parameters
defined in most of the Reports, and they're using Stored Procedures.
Any tips on how to get something like this accomplished (I'm totally in the
dark)?Are you saying you want to get existing reports in RS (retrieve the reports
from RS meta database as *.rdl file) and somehow use them with your web
application without RS available? No, the *.rdl is pretty useless without
RS, unless you can write your own report rendering engine to process *.rdl
and generate report in needed format. (but why re-invent the wheel with huge
investment?)
"Seth Williams" <sm@.here.com> wrote in message
news:ulM0%23QtgIHA.5296@.TK2MSFTNGP05.phx.gbl...
> It's going to be too long, in order to get Reporting Services, website and
> all installed here, so I'm looking for another way to get a few reports
> into production
> The reports are already done in SSRS - so I figured I could just, somehow,
> 'port' them over to our existing ASP.Net website, and use the ReportViewer
> control
> However, I've never done this, and it looks like it's not going to be as
> simple as I thought. I gather this, especially since I have parameters
> defined in most of the Reports, and they're using Stored Procedures.
> Any tips on how to get something like this accomplished (I'm totally in
> the dark)?
>|||You can convert it to an RDLC and use the ASP.NET Reportviewer control
to render it on the client without SSRS. Here's an article:
http://msdn2.microsoft.com/en-us/library/ms252109(VS.80).aspx
Jason
No comments:
Post a Comment