Reporting Services and ASP 3.0?

I currently use Crystal Reports RDC that is called from an ASP 3.0 page
(actually, the ASP page calls my custom VB COM+ code which then calls then
RDC), supplies a CustomerID as a parameter to generate a report (e.g. on one
customer) that is then exported as a PDF file and saved to the filesystem on
the server. That PDF is then available for download by end-users in my web
application (i.e. as a link). Since the move to Win2003/SQL Server 2005 one
of the Crystal components is misbehaving and I'd like to move this report
entirely to SSRS.
However, my entire web application is classic ASP 3.0 (and will not be
changing anytime soon). So what I'd like to do is call a web service with a
parameter from my ASP 3.0 page (e.g. CustomerID), have the web service
generate the report, save the PDF file on the server, and return back to the
ASP page the path to the PDF file. Except I don't know how to do this and
cannot find any examples of using ASP 3.0 with SSRS. I can probably do some
limited ASP.NET 2.0 programming to create the web service but need help
doing that (if necessary).
Can someone please direct me to examples of how to use ASP 3.0 and SSRS
together? Or tell me if I'm going about it the wrong way (e.g. do I even
need to save the PDF on the server)?
Thanks for any help or direction.If you can make web service call from your ASP3.0 app, then you can get
report from SQL Server reporting service. SQL Server RS itself provides web
services that you can use to access reports. You can consume RS's web
services at
http://ServerName/reportserver/reportservice.asmx
With this service, you call Render() method to get a report rendered as
binary data stream (in specified format, PDF, XLS, HTML..), which you can
save to file system, or send back to client's web browser. You can also call
other methods to, say, list all available reports' name for user to choose
for downloading.
"Don Miller" <nospam@.nospam.com> wrote in message
news:uGNpsgJAIHA.4612@.TK2MSFTNGP03.phx.gbl...
>I currently use Crystal Reports RDC that is called from an ASP 3.0 page
>(actually, the ASP page calls my custom VB COM+ code which then calls then
>RDC), supplies a CustomerID as a parameter to generate a report (e.g. on
>one customer) that is then exported as a PDF file and saved to the
>filesystem on the server. That PDF is then available for download by
>end-users in my web application (i.e. as a link). Since the move to
>Win2003/SQL Server 2005 one of the Crystal components is misbehaving and
>I'd like to move this report entirely to SSRS.
> However, my entire web application is classic ASP 3.0 (and will not be
> changing anytime soon). So what I'd like to do is call a web service with
> a parameter from my ASP 3.0 page (e.g. CustomerID), have the web service
> generate the report, save the PDF file on the server, and return back to
> the ASP page the path to the PDF file. Except I don't know how to do this
> and cannot find any examples of using ASP 3.0 with SSRS. I can probably do
> some limited ASP.NET 2.0 programming to create the web service but need
> help doing that (if necessary).
> Can someone please direct me to examples of how to use ASP 3.0 and SSRS
> together? Or tell me if I'm going about it the wrong way (e.g. do I even
> need to save the PDF on the server)?
> Thanks for any help or direction.
>|||On Sep 26, 6:51 pm, "Don Miller" <nos...@.nospam.com> wrote:
> I currently use Crystal Reports RDC that is called from an ASP 3.0 page
> (actually, the ASP page calls my custom VB COM+ code which then calls then
> RDC), supplies a CustomerID as a parameter to generate a report (e.g. on one
> customer) that is then exported as a PDF file and saved to the filesystem on
> the server. That PDF is then available for download by end-users in my web
> application (i.e. as a link). Since the move to Win2003/SQL Server 2005 one
> of the Crystal components is misbehaving and I'd like to move this report
> entirely to SSRS.
> However, my entire web application is classic ASP 3.0 (and will not be
> changing anytime soon). So what I'd like to do is call a web service with a
> parameter from my ASP 3.0 page (e.g. CustomerID), have the web service
> generate the report, save the PDF file on the server, and return back to the
> ASP page the path to the PDF file. Except I don't know how to do this and
> cannot find any examples of using ASP 3.0 with SSRS. I can probably do some
> limited ASP.NET 2.0 programming to create the web service but need help
> doing that (if necessary).
> Can someone please direct me to examples of how to use ASP 3.0 and SSRS
> together? Or tell me if I'm going about it the wrong way (e.g. do I even
> need to save the PDF on the server)?
> Thanks for any help or direction.
You can either iFrame a connection to the Report Server and/or you can
access a report and export it to a predefined format via URL from
within ASP 3.0. Here's an example of calling a report and exporting it
to PDF and separately to Excel.
http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=PDF
http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=Excel
Here's the URL format:
http://<ServerName>/reportserver?/<Directory>/<ReportName>&rs:Command=Render&<ParameterName>=<ParameterValue>&rs:Format=<PDF/CSV/XML/Excel/MHTML>
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Thanks for the pointer.
But how do I specify where the PDF file is created (or is that hard-coded
into the web service?)?
And how would I get back the physical path (including filename) of the PDF
file?
I'm really new at web services and I realize these questions may be naive.
Thanks again.
"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:1190854577.900501.137650@.w3g2000hsg.googlegroups.com...
> On Sep 26, 6:51 pm, "Don Miller" <nos...@.nospam.com> wrote:
>> I currently use Crystal Reports RDC that is called from an ASP 3.0 page
>> (actually, the ASP page calls my custom VB COM+ code which then calls
>> then
>> RDC), supplies a CustomerID as a parameter to generate a report (e.g. on
>> one
>> customer) that is then exported as a PDF file and saved to the filesystem
>> on
>> the server. That PDF is then available for download by end-users in my
>> web
>> application (i.e. as a link). Since the move to Win2003/SQL Server 2005
>> one
>> of the Crystal components is misbehaving and I'd like to move this report
>> entirely to SSRS.
>> However, my entire web application is classic ASP 3.0 (and will not be
>> changing anytime soon). So what I'd like to do is call a web service with
>> a
>> parameter from my ASP 3.0 page (e.g. CustomerID), have the web service
>> generate the report, save the PDF file on the server, and return back to
>> the
>> ASP page the path to the PDF file. Except I don't know how to do this and
>> cannot find any examples of using ASP 3.0 with SSRS. I can probably do
>> some
>> limited ASP.NET 2.0 programming to create the web service but need help
>> doing that (if necessary).
>> Can someone please direct me to examples of how to use ASP 3.0 and SSRS
>> together? Or tell me if I'm going about it the wrong way (e.g. do I even
>> need to save the PDF on the server)?
>> Thanks for any help or direction.
>
> You can either iFrame a connection to the Report Server and/or you can
> access a report and export it to a predefined format via URL from
> within ASP 3.0. Here's an example of calling a report and exporting it
> to PDF and separately to Excel.
> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=PDF
> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=Excel
> Here's the URL format:
> http://<ServerName>/reportserver?/<Directory>/<ReportName>&rs:Command=Render&<ParameterName>=<ParameterValue>&rs:Format=<PDF/CSV/XML/Excel/MHTML>
> Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||Unless you need to I would not go to PDF. RS can render in multiple ways but
PDF and Excel are the slowest. It is not saving the file anywhere, it is
streaming it to you.
You can integrate in two ways, web services or URL integration. If you use
URL integration (the easiest) then the user can get the full benefit of the
server including printing support and they have have html output as the
rendering type which is much much faster than pdf. In books online the
documentation is quite good (RS 2005). If you are using RS 2000 then go to
the MS site and look at the books on line there for RS 2005. URL integration
has not changed between versions. For example, here is an example URL that
sends a parameter. Your app would just assemble the URL. I strongly
recommend starting this way. Otherwise I see a very large learning curve for
you. You need to learn and understand Reporting Services. With URL
integration you can concentrate on that without worrying about webservices
from asp 3.0 website.
Here are some quick examples. I show below different rendering as well:
Excel, PDF and the default HTML.
This renders as Excel
http://servername/reportserver?/Sales/YearlySalesSummary&rs:Format=ExcelThis
renders as PDF and passes a parameter for the year
http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006&rs:Format=PDFThis
renders as HTML (the speediest) which is the default if nothing is
specified.
http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006When
integrating with older technology URL integration in my mind is the way to
go.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Don Miller" <nospam@.nospam.com> wrote in message
news:elTFOiLAIHA.464@.TK2MSFTNGP02.phx.gbl...
> Thanks for the pointer.
> But how do I specify where the PDF file is created (or is that hard-coded
> into the web service?)?
> And how would I get back the physical path (including filename) of the PDF
> file?
> I'm really new at web services and I realize these questions may be naive.
> Thanks again.
> "EMartinez" <emartinez.pr1@.gmail.com> wrote in message
> news:1190854577.900501.137650@.w3g2000hsg.googlegroups.com...
>> On Sep 26, 6:51 pm, "Don Miller" <nos...@.nospam.com> wrote:
>> I currently use Crystal Reports RDC that is called from an ASP 3.0 page
>> (actually, the ASP page calls my custom VB COM+ code which then calls
>> then
>> RDC), supplies a CustomerID as a parameter to generate a report (e.g. on
>> one
>> customer) that is then exported as a PDF file and saved to the
>> filesystem on
>> the server. That PDF is then available for download by end-users in my
>> web
>> application (i.e. as a link). Since the move to Win2003/SQL Server 2005
>> one
>> of the Crystal components is misbehaving and I'd like to move this
>> report
>> entirely to SSRS.
>> However, my entire web application is classic ASP 3.0 (and will not be
>> changing anytime soon). So what I'd like to do is call a web service
>> with a
>> parameter from my ASP 3.0 page (e.g. CustomerID), have the web service
>> generate the report, save the PDF file on the server, and return back to
>> the
>> ASP page the path to the PDF file. Except I don't know how to do this
>> and
>> cannot find any examples of using ASP 3.0 with SSRS. I can probably do
>> some
>> limited ASP.NET 2.0 programming to create the web service but need help
>> doing that (if necessary).
>> Can someone please direct me to examples of how to use ASP 3.0 and SSRS
>> together? Or tell me if I'm going about it the wrong way (e.g. do I even
>> need to save the PDF on the server)?
>> Thanks for any help or direction.
>>
>> You can either iFrame a connection to the Report Server and/or you can
>> access a report and export it to a predefined format via URL from
>> within ASP 3.0. Here's an example of calling a report and exporting it
>> to PDF and separately to Excel.
>> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=PDF
>> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=Excel
>> Here's the URL format:
>> http://<ServerName>/reportserver?/<Directory>/<ReportName>&rs:Command=Render&<ParameterName>=<ParameterValue>&rs:Format=<PDF/CSV/XML/Excel/MHTML>
>> Hope this helps.
>> Regards,
>> Enrique Martinez
>> Sr. Software Consultant
>|||Thanks for your time putting this together and your advice.
Unfortunately, I do "need" a PDF as a file that can be downloaded and saved
to device (disk, network share, flash drive, etc.) by my customers for their
permanent and legal records (I tell them to right-click my link and "Save
Target As..." to do the save, rather than rely on Adobe Reader Disk Save
icon). This is a fundamental business requirement.
Also, the report is usually 8-10 page long and contains about a dozen
sub-reports all with different and intricate formatting that cannot be
duplicated with HTML (even if I wanted to save in that format). And it does
currently takes about 5-10secs to generate (it basically takes ALL the
information about a customer in the database and exports it).
So, if I understand you, even in the best of circumstances, the exported PDF
document is not ever saved physically to disk on the server? This might
still work as long as my customer *could* save it with Adobe Reader in the
browser.
> Otherwise I see a very large learning curve for you.
Do you know of anyone who has already climbed that mountain who I could
contract to provide the framework for accessing exported PDF files from SSRS
from ASP 3.0?
And if you don't, do you know of any other references that I could begin
climbing?
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:uOzg3KRAIHA.464@.TK2MSFTNGP02.phx.gbl...
> Unless you need to I would not go to PDF. RS can render in multiple ways
> but PDF and Excel are the slowest. It is not saving the file anywhere, it
> is streaming it to you.
> You can integrate in two ways, web services or URL integration. If you use
> URL integration (the easiest) then the user can get the full benefit of
> the server including printing support and they have have html output as
> the rendering type which is much much faster than pdf. In books online the
> documentation is quite good (RS 2005). If you are using RS 2000 then go to
> the MS site and look at the books on line there for RS 2005. URL
> integration has not changed between versions. For example, here is an
> example URL that sends a parameter. Your app would just assemble the URL.
> I strongly recommend starting this way. Otherwise I see a very large
> learning curve for you. You need to learn and understand Reporting
> Services. With URL integration you can concentrate on that without
> worrying about webservices from asp 3.0 website.
> Here are some quick examples. I show below different rendering as well:
> Excel, PDF and the default HTML.
> This renders as Excel
> http://servername/reportserver?/Sales/YearlySalesSummary&rs:Format=ExcelThis
> renders as PDF and passes a parameter for the year
> http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006&rs:Format=PDFThis
> renders as HTML (the speediest) which is the default if nothing is
> specified.
> http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006When
> integrating with older technology URL integration in my mind is the way to
> go.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Don Miller" <nospam@.nospam.com> wrote in message
> news:elTFOiLAIHA.464@.TK2MSFTNGP02.phx.gbl...
>> Thanks for the pointer.
>> But how do I specify where the PDF file is created (or is that hard-coded
>> into the web service?)?
>> And how would I get back the physical path (including filename) of the
>> PDF file?
>> I'm really new at web services and I realize these questions may be
>> naive. Thanks again.
>> "EMartinez" <emartinez.pr1@.gmail.com> wrote in message
>> news:1190854577.900501.137650@.w3g2000hsg.googlegroups.com...
>> On Sep 26, 6:51 pm, "Don Miller" <nos...@.nospam.com> wrote:
>> I currently use Crystal Reports RDC that is called from an ASP 3.0 page
>> (actually, the ASP page calls my custom VB COM+ code which then calls
>> then
>> RDC), supplies a CustomerID as a parameter to generate a report (e.g.
>> on one
>> customer) that is then exported as a PDF file and saved to the
>> filesystem on
>> the server. That PDF is then available for download by end-users in my
>> web
>> application (i.e. as a link). Since the move to Win2003/SQL Server 2005
>> one
>> of the Crystal components is misbehaving and I'd like to move this
>> report
>> entirely to SSRS.
>> However, my entire web application is classic ASP 3.0 (and will not be
>> changing anytime soon). So what I'd like to do is call a web service
>> with a
>> parameter from my ASP 3.0 page (e.g. CustomerID), have the web service
>> generate the report, save the PDF file on the server, and return back
>> to the
>> ASP page the path to the PDF file. Except I don't know how to do this
>> and
>> cannot find any examples of using ASP 3.0 with SSRS. I can probably do
>> some
>> limited ASP.NET 2.0 programming to create the web service but need help
>> doing that (if necessary).
>> Can someone please direct me to examples of how to use ASP 3.0 and SSRS
>> together? Or tell me if I'm going about it the wrong way (e.g. do I
>> even
>> need to save the PDF on the server)?
>> Thanks for any help or direction.
>>
>> You can either iFrame a connection to the Report Server and/or you can
>> access a report and export it to a predefined format via URL from
>> within ASP 3.0. Here's an example of calling a report and exporting it
>> to PDF and separately to Excel.
>> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=PDF
>> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=Excel
>> Here's the URL format:
>> http://<ServerName>/reportserver?/<Directory>/<ReportName>&rs:Command=Render&<ParameterName>=<ParameterValue>&rs:Format=<PDF/CSV/XML/Excel/MHTML>
>> Hope this helps.
>> Regards,
>> Enrique Martinez
>> Sr. Software Consultant
>>
>|||If you use URL integration you get the full Report Manager (the portal that
ships with RS) interface. This allows the user to save as in any of the
formats. So, they get very fast html for viewing and they can save as they
want when they want in a variety of formats. IF you pick PDF (which the
example showed) then what happens is the PDF is viewed in the browser. They
can save or they can export as PDF.
Nothing prevents you from using PDF as your design target. There are
definitely things you can do in PDF that you cannot do in html format.
However, when developing this means you will need to do lots of deploying
and viewing. The development environment preview is html.
You are a little stuck with how the previous environment worked. RS is
streaming the result back to the browser. The browser is the target. You can
change the rendering format but it still gets streamed to the browser
whether it is Excel, PDF, html, image whatever and then IE determines how to
handle it. PDF will get a File Download box. If you want to save to disk on
the server your app would have to take the stream and write it to disk.
You also with URL integration have control over which parts of the screen to
show, for instance the parameter section. RS comes with the ability to
export in multiple formats and to print.
My suggestion is that before you go too much further worry about how to
integrate that you first learn about RS. Create a few simple (very simple)
reports. Try creating the URL and just typing it into the browser. Do
different things by modifying the URL. Save your example URLs off. Once you
know the capabilities of doing this you can decide if you need to go more
extreme and implement web services.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Don Miller" <nospam@.nospam.com> wrote in message
news:OOkUblRAIHA.3548@.TK2MSFTNGP06.phx.gbl...
> Thanks for your time putting this together and your advice.
> Unfortunately, I do "need" a PDF as a file that can be downloaded and
> saved to device (disk, network share, flash drive, etc.) by my customers
> for their permanent and legal records (I tell them to right-click my link
> and "Save Target As..." to do the save, rather than rely on Adobe Reader
> Disk Save icon). This is a fundamental business requirement.
> Also, the report is usually 8-10 page long and contains about a dozen
> sub-reports all with different and intricate formatting that cannot be
> duplicated with HTML (even if I wanted to save in that format). And it
> does currently takes about 5-10secs to generate (it basically takes ALL
> the information about a customer in the database and exports it).
> So, if I understand you, even in the best of circumstances, the exported
> PDF document is not ever saved physically to disk on the server? This
> might still work as long as my customer *could* save it with Adobe Reader
> in the browser.
>> Otherwise I see a very large learning curve for you.
> Do you know of anyone who has already climbed that mountain who I could
> contract to provide the framework for accessing exported PDF files from
> SSRS from ASP 3.0?
> And if you don't, do you know of any other references that I could begin
> climbing?
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:uOzg3KRAIHA.464@.TK2MSFTNGP02.phx.gbl...
>> Unless you need to I would not go to PDF. RS can render in multiple ways
>> but PDF and Excel are the slowest. It is not saving the file anywhere, it
>> is streaming it to you.
>> You can integrate in two ways, web services or URL integration. If you
>> use URL integration (the easiest) then the user can get the full benefit
>> of the server including printing support and they have have html output
>> as the rendering type which is much much faster than pdf. In books online
>> the documentation is quite good (RS 2005). If you are using RS 2000 then
>> go to the MS site and look at the books on line there for RS 2005. URL
>> integration has not changed between versions. For example, here is an
>> example URL that sends a parameter. Your app would just assemble the URL.
>> I strongly recommend starting this way. Otherwise I see a very large
>> learning curve for you. You need to learn and understand Reporting
>> Services. With URL integration you can concentrate on that without
>> worrying about webservices from asp 3.0 website.
>> Here are some quick examples. I show below different rendering as well:
>> Excel, PDF and the default HTML.
>> This renders as Excel
>> http://servername/reportserver?/Sales/YearlySalesSummary&rs:Format=ExcelThis
>> renders as PDF and passes a parameter for the year
>> http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006&rs:Format=PDFThis
>> renders as HTML (the speediest) which is the default if nothing is
>> specified.
>> http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006When
>> integrating with older technology URL integration in my mind is the way
>> to go.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Don Miller" <nospam@.nospam.com> wrote in message
>> news:elTFOiLAIHA.464@.TK2MSFTNGP02.phx.gbl...
>> Thanks for the pointer.
>> But how do I specify where the PDF file is created (or is that
>> hard-coded into the web service?)?
>> And how would I get back the physical path (including filename) of the
>> PDF file?
>> I'm really new at web services and I realize these questions may be
>> naive. Thanks again.
>> "EMartinez" <emartinez.pr1@.gmail.com> wrote in message
>> news:1190854577.900501.137650@.w3g2000hsg.googlegroups.com...
>> On Sep 26, 6:51 pm, "Don Miller" <nos...@.nospam.com> wrote:
>> I currently use Crystal Reports RDC that is called from an ASP 3.0
>> page
>> (actually, the ASP page calls my custom VB COM+ code which then calls
>> then
>> RDC), supplies a CustomerID as a parameter to generate a report (e.g.
>> on one
>> customer) that is then exported as a PDF file and saved to the
>> filesystem on
>> the server. That PDF is then available for download by end-users in my
>> web
>> application (i.e. as a link). Since the move to Win2003/SQL Server
>> 2005 one
>> of the Crystal components is misbehaving and I'd like to move this
>> report
>> entirely to SSRS.
>> However, my entire web application is classic ASP 3.0 (and will not be
>> changing anytime soon). So what I'd like to do is call a web service
>> with a
>> parameter from my ASP 3.0 page (e.g. CustomerID), have the web service
>> generate the report, save the PDF file on the server, and return back
>> to the
>> ASP page the path to the PDF file. Except I don't know how to do this
>> and
>> cannot find any examples of using ASP 3.0 with SSRS. I can probably do
>> some
>> limited ASP.NET 2.0 programming to create the web service but need
>> help
>> doing that (if necessary).
>> Can someone please direct me to examples of how to use ASP 3.0 and
>> SSRS
>> together? Or tell me if I'm going about it the wrong way (e.g. do I
>> even
>> need to save the PDF on the server)?
>> Thanks for any help or direction.
>>
>> You can either iFrame a connection to the Report Server and/or you can
>> access a report and export it to a predefined format via URL from
>> within ASP 3.0. Here's an example of calling a report and exporting it
>> to PDF and separately to Excel.
>> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=PDF
>> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=Excel
>> Here's the URL format:
>> http://<ServerName>/reportserver?/<Directory>/<ReportName>&rs:Command=Render&<ParameterName>=<ParameterValue>&rs:Format=<PDF/CSV/XML/Excel/MHTML>
>> Hope this helps.
>> Regards,
>> Enrique Martinez
>> Sr. Software Consultant
>>
>>
>|||Thanks. I certainly am stuck in the mindset I've had and used successfully
for the last seven years. Time to change maybe.
Although saving the report as PDF to a device is optional (but necessary),
most of my customers click on the link to the PDF file (on the server) on my
web page and it loads into Adobe Reader plug-in and they simply print out
the PDF document and save *that* paper as their permanent record. So, a
"file download" box appearing first would not be a good thing for most
customers (but I assume there will be an Open instead option with
configuration of the response headers?).
I actually do NOT want to expose my customers to the full Report Manager at
all or give them options to save the report in any other format. They just
want one thing and many of my end-users would be overwhelmed by anything
other than "click here" to view the report. These are not business people
and many only have high-school diplomas and "variety" is not good.
Nevertheless, I'll take your seasoned advice and play around a bit. But with
this and all the hacking that has to be done (no Report Headers/Footers
without tricks, hidden parameters, no Fields in Page Headers, no tabs, no
document size editing, etc.) to recreate a Crystal Reports report, I may be
going right back to CR. I hope not though.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:uN2MBBSAIHA.4444@.TK2MSFTNGP03.phx.gbl...
> If you use URL integration you get the full Report Manager (the portal
> that ships with RS) interface. This allows the user to save as in any of
> the formats. So, they get very fast html for viewing and they can save as
> they want when they want in a variety of formats. IF you pick PDF (which
> the example showed) then what happens is the PDF is viewed in the browser.
> They can save or they can export as PDF.
> Nothing prevents you from using PDF as your design target. There are
> definitely things you can do in PDF that you cannot do in html format.
> However, when developing this means you will need to do lots of deploying
> and viewing. The development environment preview is html.
> You are a little stuck with how the previous environment worked. RS is
> streaming the result back to the browser. The browser is the target. You
> can change the rendering format but it still gets streamed to the browser
> whether it is Excel, PDF, html, image whatever and then IE determines how
> to handle it. PDF will get a File Download box. If you want to save to
> disk on the server your app would have to take the stream and write it to
> disk.
> You also with URL integration have control over which parts of the screen
> to show, for instance the parameter section. RS comes with the ability to
> export in multiple formats and to print.
> My suggestion is that before you go too much further worry about how to
> integrate that you first learn about RS. Create a few simple (very simple)
> reports. Try creating the URL and just typing it into the browser. Do
> different things by modifying the URL. Save your example URLs off. Once
> you know the capabilities of doing this you can decide if you need to go
> more extreme and implement web services.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Don Miller" <nospam@.nospam.com> wrote in message
> news:OOkUblRAIHA.3548@.TK2MSFTNGP06.phx.gbl...
>> Thanks for your time putting this together and your advice.
>> Unfortunately, I do "need" a PDF as a file that can be downloaded and
>> saved to device (disk, network share, flash drive, etc.) by my customers
>> for their permanent and legal records (I tell them to right-click my link
>> and "Save Target As..." to do the save, rather than rely on Adobe Reader
>> Disk Save icon). This is a fundamental business requirement.
>> Also, the report is usually 8-10 page long and contains about a dozen
>> sub-reports all with different and intricate formatting that cannot be
>> duplicated with HTML (even if I wanted to save in that format). And it
>> does currently takes about 5-10secs to generate (it basically takes ALL
>> the information about a customer in the database and exports it).
>> So, if I understand you, even in the best of circumstances, the exported
>> PDF document is not ever saved physically to disk on the server? This
>> might still work as long as my customer *could* save it with Adobe Reader
>> in the browser.
>> Otherwise I see a very large learning curve for you.
>> Do you know of anyone who has already climbed that mountain who I could
>> contract to provide the framework for accessing exported PDF files from
>> SSRS from ASP 3.0?
>> And if you don't, do you know of any other references that I could begin
>> climbing?
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:uOzg3KRAIHA.464@.TK2MSFTNGP02.phx.gbl...
>> Unless you need to I would not go to PDF. RS can render in multiple ways
>> but PDF and Excel are the slowest. It is not saving the file anywhere,
>> it is streaming it to you.
>> You can integrate in two ways, web services or URL integration. If you
>> use URL integration (the easiest) then the user can get the full benefit
>> of the server including printing support and they have have html output
>> as the rendering type which is much much faster than pdf. In books
>> online the documentation is quite good (RS 2005). If you are using RS
>> 2000 then go to the MS site and look at the books on line there for RS
>> 2005. URL integration has not changed between versions. For example,
>> here is an example URL that sends a parameter. Your app would just
>> assemble the URL. I strongly recommend starting this way. Otherwise I
>> see a very large learning curve for you. You need to learn and
>> understand Reporting Services. With URL integration you can concentrate
>> on that without worrying about webservices from asp 3.0 website.
>> Here are some quick examples. I show below different rendering as well:
>> Excel, PDF and the default HTML.
>> This renders as Excel
>> http://servername/reportserver?/Sales/YearlySalesSummary&rs:Format=ExcelThis
>> renders as PDF and passes a parameter for the year
>> http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006&rs:Format=PDFThis
>> renders as HTML (the speediest) which is the default if nothing is
>> specified.
>> http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006When
>> integrating with older technology URL integration in my mind is the way
>> to go.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Don Miller" <nospam@.nospam.com> wrote in message
>> news:elTFOiLAIHA.464@.TK2MSFTNGP02.phx.gbl...
>> Thanks for the pointer.
>> But how do I specify where the PDF file is created (or is that
>> hard-coded into the web service?)?
>> And how would I get back the physical path (including filename) of the
>> PDF file?
>> I'm really new at web services and I realize these questions may be
>> naive. Thanks again.
>> "EMartinez" <emartinez.pr1@.gmail.com> wrote in message
>> news:1190854577.900501.137650@.w3g2000hsg.googlegroups.com...
>> On Sep 26, 6:51 pm, "Don Miller" <nos...@.nospam.com> wrote:
>> I currently use Crystal Reports RDC that is called from an ASP 3.0
>> page
>> (actually, the ASP page calls my custom VB COM+ code which then calls
>> then
>> RDC), supplies a CustomerID as a parameter to generate a report (e.g.
>> on one
>> customer) that is then exported as a PDF file and saved to the
>> filesystem on
>> the server. That PDF is then available for download by end-users in
>> my web
>> application (i.e. as a link). Since the move to Win2003/SQL Server
>> 2005 one
>> of the Crystal components is misbehaving and I'd like to move this
>> report
>> entirely to SSRS.
>> However, my entire web application is classic ASP 3.0 (and will not
>> be
>> changing anytime soon). So what I'd like to do is call a web service
>> with a
>> parameter from my ASP 3.0 page (e.g. CustomerID), have the web
>> service
>> generate the report, save the PDF file on the server, and return back
>> to the
>> ASP page the path to the PDF file. Except I don't know how to do this
>> and
>> cannot find any examples of using ASP 3.0 with SSRS. I can probably
>> do some
>> limited ASP.NET 2.0 programming to create the web service but need
>> help
>> doing that (if necessary).
>> Can someone please direct me to examples of how to use ASP 3.0 and
>> SSRS
>> together? Or tell me if I'm going about it the wrong way (e.g. do I
>> even
>> need to save the PDF on the server)?
>> Thanks for any help or direction.
>>
>> You can either iFrame a connection to the Report Server and/or you can
>> access a report and export it to a predefined format via URL from
>> within ASP 3.0. Here's an example of calling a report and exporting it
>> to PDF and separately to Excel.
>> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=PDF
>> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=Excel
>> Here's the URL format:
>> http://<ServerName>/reportserver?/<Directory>/<ReportName>&rs:Command=Render&<ParameterName>=<ParameterValue>&rs:Format=<PDF/CSV/XML/Excel/MHTML>
>> Hope this helps.
>> Regards,
>> Enrique Martinez
>> Sr. Software Consultant
>>
>>
>>
>|||After very brief playing, with the complete URL, this may indeed work (and
save me the trouble of deleting PDFs off the server every night - with a BAT
file ;) BUT I need to have the default filename to be saved to be specific
when folks save the exported file (see other Topic I've posted).
It's always something ;)
"Don Miller" <nospam@.nospam.com> wrote in message
news:u6ZWUQSAIHA.4592@.TK2MSFTNGP03.phx.gbl...
> Thanks. I certainly am stuck in the mindset I've had and used successfully
> for the last seven years. Time to change maybe.
> Although saving the report as PDF to a device is optional (but necessary),
> most of my customers click on the link to the PDF file (on the server) on
> my web page and it loads into Adobe Reader plug-in and they simply print
> out the PDF document and save *that* paper as their permanent record. So,
> a "file download" box appearing first would not be a good thing for most
> customers (but I assume there will be an Open instead option with
> configuration of the response headers?).
> I actually do NOT want to expose my customers to the full Report Manager
> at all or give them options to save the report in any other format. They
> just want one thing and many of my end-users would be overwhelmed by
> anything other than "click here" to view the report. These are not
> business people and many only have high-school diplomas and "variety" is
> not good.
> Nevertheless, I'll take your seasoned advice and play around a bit. But
> with this and all the hacking that has to be done (no Report
> Headers/Footers without tricks, hidden parameters, no Fields in Page
> Headers, no tabs, no document size editing, etc.) to recreate a Crystal
> Reports report, I may be going right back to CR. I hope not though.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:uN2MBBSAIHA.4444@.TK2MSFTNGP03.phx.gbl...
>> If you use URL integration you get the full Report Manager (the portal
>> that ships with RS) interface. This allows the user to save as in any of
>> the formats. So, they get very fast html for viewing and they can save as
>> they want when they want in a variety of formats. IF you pick PDF (which
>> the example showed) then what happens is the PDF is viewed in the
>> browser. They can save or they can export as PDF.
>> Nothing prevents you from using PDF as your design target. There are
>> definitely things you can do in PDF that you cannot do in html format.
>> However, when developing this means you will need to do lots of deploying
>> and viewing. The development environment preview is html.
>> You are a little stuck with how the previous environment worked. RS is
>> streaming the result back to the browser. The browser is the target. You
>> can change the rendering format but it still gets streamed to the browser
>> whether it is Excel, PDF, html, image whatever and then IE determines how
>> to handle it. PDF will get a File Download box. If you want to save to
>> disk on the server your app would have to take the stream and write it to
>> disk.
>> You also with URL integration have control over which parts of the screen
>> to show, for instance the parameter section. RS comes with the ability to
>> export in multiple formats and to print.
>> My suggestion is that before you go too much further worry about how to
>> integrate that you first learn about RS. Create a few simple (very
>> simple) reports. Try creating the URL and just typing it into the
>> browser. Do different things by modifying the URL. Save your example URLs
>> off. Once you know the capabilities of doing this you can decide if you
>> need to go more extreme and implement web services.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Don Miller" <nospam@.nospam.com> wrote in message
>> news:OOkUblRAIHA.3548@.TK2MSFTNGP06.phx.gbl...
>> Thanks for your time putting this together and your advice.
>> Unfortunately, I do "need" a PDF as a file that can be downloaded and
>> saved to device (disk, network share, flash drive, etc.) by my customers
>> for their permanent and legal records (I tell them to right-click my
>> link and "Save Target As..." to do the save, rather than rely on Adobe
>> Reader Disk Save icon). This is a fundamental business requirement.
>> Also, the report is usually 8-10 page long and contains about a dozen
>> sub-reports all with different and intricate formatting that cannot be
>> duplicated with HTML (even if I wanted to save in that format). And it
>> does currently takes about 5-10secs to generate (it basically takes ALL
>> the information about a customer in the database and exports it).
>> So, if I understand you, even in the best of circumstances, the exported
>> PDF document is not ever saved physically to disk on the server? This
>> might still work as long as my customer *could* save it with Adobe
>> Reader in the browser.
>> Otherwise I see a very large learning curve for you.
>> Do you know of anyone who has already climbed that mountain who I could
>> contract to provide the framework for accessing exported PDF files from
>> SSRS from ASP 3.0?
>> And if you don't, do you know of any other references that I could begin
>> climbing?
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:uOzg3KRAIHA.464@.TK2MSFTNGP02.phx.gbl...
>> Unless you need to I would not go to PDF. RS can render in multiple
>> ways but PDF and Excel are the slowest. It is not saving the file
>> anywhere, it is streaming it to you.
>> You can integrate in two ways, web services or URL integration. If you
>> use URL integration (the easiest) then the user can get the full
>> benefit of the server including printing support and they have have
>> html output as the rendering type which is much much faster than pdf.
>> In books online the documentation is quite good (RS 2005). If you are
>> using RS 2000 then go to the MS site and look at the books on line
>> there for RS 2005. URL integration has not changed between versions.
>> For example, here is an example URL that sends a parameter. Your app
>> would just assemble the URL. I strongly recommend starting this way.
>> Otherwise I see a very large learning curve for you. You need to learn
>> and understand Reporting Services. With URL integration you can
>> concentrate on that without worrying about webservices from asp 3.0
>> website.
>> Here are some quick examples. I show below different rendering as well:
>> Excel, PDF and the default HTML.
>> This renders as Excel
>> http://servername/reportserver?/Sales/YearlySalesSummary&rs:Format=ExcelThis
>> renders as PDF and passes a parameter for the year
>> http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006&rs:Format=PDFThis
>> renders as HTML (the speediest) which is the default if nothing is
>> specified.
>> http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006When
>> integrating with older technology URL integration in my mind is the way
>> to go.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Don Miller" <nospam@.nospam.com> wrote in message
>> news:elTFOiLAIHA.464@.TK2MSFTNGP02.phx.gbl...
>> Thanks for the pointer.
>> But how do I specify where the PDF file is created (or is that
>> hard-coded into the web service?)?
>> And how would I get back the physical path (including filename) of the
>> PDF file?
>> I'm really new at web services and I realize these questions may be
>> naive. Thanks again.
>> "EMartinez" <emartinez.pr1@.gmail.com> wrote in message
>> news:1190854577.900501.137650@.w3g2000hsg.googlegroups.com...
>> On Sep 26, 6:51 pm, "Don Miller" <nos...@.nospam.com> wrote:
>>> I currently use Crystal Reports RDC that is called from an ASP 3.0
>>> page
>>> (actually, the ASP page calls my custom VB COM+ code which then
>>> calls then
>>> RDC), supplies a CustomerID as a parameter to generate a report
>>> (e.g. on one
>>> customer) that is then exported as a PDF file and saved to the
>>> filesystem on
>>> the server. That PDF is then available for download by end-users in
>>> my web
>>> application (i.e. as a link). Since the move to Win2003/SQL Server
>>> 2005 one
>>> of the Crystal components is misbehaving and I'd like to move this
>>> report
>>> entirely to SSRS.
>>>
>>> However, my entire web application is classic ASP 3.0 (and will not
>>> be
>>> changing anytime soon). So what I'd like to do is call a web service
>>> with a
>>> parameter from my ASP 3.0 page (e.g. CustomerID), have the web
>>> service
>>> generate the report, save the PDF file on the server, and return
>>> back to the
>>> ASP page the path to the PDF file. Except I don't know how to do
>>> this and
>>> cannot find any examples of using ASP 3.0 with SSRS. I can probably
>>> do some
>>> limited ASP.NET 2.0 programming to create the web service but need
>>> help
>>> doing that (if necessary).
>>>
>>> Can someone please direct me to examples of how to use ASP 3.0 and
>>> SSRS
>>> together? Or tell me if I'm going about it the wrong way (e.g. do I
>>> even
>>> need to save the PDF on the server)?
>>>
>>> Thanks for any help or direction.
>>
>> You can either iFrame a connection to the Report Server and/or you
>> can
>> access a report and export it to a predefined format via URL from
>> within ASP 3.0. Here's an example of calling a report and exporting
>> it
>> to PDF and separately to Excel.
>> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=PDF
>> http://SomeServerName/reportserver?/SomeReportFolder/SomeReportName&rs:Command=Render&Param1=ParamValue&rs:Format=Excel
>> Here's the URL format:
>> http://<ServerName>/reportserver?/<Directory>/<ReportName>&rs:Command=Render&<ParameterName>=<ParameterValue>&rs:Format=<PDF/CSV/XML/Excel/MHTML>
>> Hope this helps.
>> Regards,
>> Enrique Martinez
>> Sr. Software Consultant
>>
>>
>>
>>
>|||On Sep 27, 12:12 pm, "Don Miller" <nos...@.nospam.com> wrote:
> After very brief playing, with the complete URL, this may indeed work (and
> save me the trouble of deleting PDFs off the server every night - with a =BAT
> file ;) BUT I need to have the default filename to be saved to be specific
> when folks save the exported file (see other Topic I've posted).
> It's always something ;)
> "Don Miller" <nos...@.nospam.com> wrote in message
> news:u6ZWUQSAIHA.4592@.TK2MSFTNGP03.phx.gbl...
> > Thanks. I certainly am stuck in the mindset I've had and used successfu=lly
> > for the last seven years. Time to change maybe.
> > Although saving the report as PDF to a device is optional (but necessar=y),
> > most of my customers click on the link to the PDF file (on the server) =on
> > my web page and it loads into Adobe Reader plug-in and they simply print
> > out the PDF document and save *that* paper as their permanent record. S=o,
> > a "file download" box appearing first would not be a good thing for most
> > customers (but I assume there will be an Open instead option with
> > configuration of the response headers?).
> > I actually do NOT want to expose my customers to the full Report Manager
> > at all or give them options to save the report in any other format. They
> > just want one thing and many of my end-users would be overwhelmed by
> > anything other than "click here" to view the report. These are not
> > business people and many only have high-school diplomas and "variety" is
> > not good.
> > Nevertheless, I'll take your seasoned advice and play around a bit. But
> > with this and all the hacking that has to be done (no Report
> > Headers/Footers without tricks, hidden parameters, no Fields in Page
> > Headers, no tabs, no document size editing, etc.) to recreate a Crystal
> > Reports report, I may be going right back to CR. I hope not though.
> > "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com> wrote in message
> >news:uN2MBBSAIHA.4444@.TK2MSFTNGP03.phx.gbl...
> >> If you use URL integration you get the full Report Manager (the portal
> >> that ships with RS) interface. This allows the user to save as in any =of
> >> the formats. So, they get very fast html for viewing and they can save= as
> >> they want when they want in a variety of formats. IF you pick PDF (whi=ch
> >> the example showed) then what happens is the PDF is viewed in the
> >> browser. They can save or they can export as PDF.
> >> Nothing prevents you from using PDF as your design target. There are
> >> definitely things you can do in PDF that you cannot do in html format.
> >> However, when developing this means you will need to do lots of deploy=ing
> >> and viewing. The development environment preview is html.
> >> You are a little stuck with how the previous environment worked. RS is
> >> streaming the result back to the browser. The browser is the target. Y=ou
> >> can change the rendering format but it still gets streamed to the brow=ser
> >> whether it is Excel, PDF, html, image whatever and then IE determines =how
> >> to handle it. PDF will get a File Download box. If you want to save to
> >> disk on the server your app would have to take the stream and write it= to
> >> disk.
> >> You also with URL integration have control over which parts of the scr=een
> >> to show, for instance the parameter section. RS comes with the ability= to
> >> export in multiple formats and to print.
> >> My suggestion is that before you go too much further worry about how to
> >> integrate that you first learn about RS. Create a few simple (very
> >> simple) reports. Try creating the URL and just typing it into the
> >> browser. Do different things by modifying the URL. Save your example U=RLs
> >> off. Once you know the capabilities of doing this you can decide if you
> >> need to go more extreme and implement web services.
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >> "Don Miller" <nos...@.nospam.com> wrote in message
> >>news:OOkUblRAIHA.3548@.TK2MSFTNGP06.phx.gbl...
> >> Thanks for your time putting this together and your advice.
> >> Unfortunately, I do "need" a PDF as a file that can be downloaded and
> >> saved to device (disk, network share, flash drive, etc.) by my custom=ers
> >> for their permanent and legal records (I tell them to right-click my
> >> link and "Save Target As..." to do the save, rather than rely on Adobe
> >> Reader Disk Save icon). This is a fundamental business requirement.
> >> Also, the report is usually 8-10 page long and contains about a dozen
> >> sub-reports all with different and intricate formatting that cannot be
> >> duplicated with HTML (even if I wanted to save in that format). And it
> >> does currently takes about 5-10secs to generate (it basically takes A=LL
> >> the information about a customer in the database and exports it).
> >> So, if I understand you, even in the best of circumstances, the expor=ted
> >> PDF document is not ever saved physically to disk on the server? This
> >> might still work as long as my customer *could* save it with Adobe
> >> Reader in the browser.
> >> Otherwise I see a very large learning curve for you.
> >> Do you know of anyone who has already climbed that mountain who I cou=ld
> >> contract to provide the framework for accessing exported PDF files fr=om
> >> SSRS from ASP 3.0?
> >> And if you don't, do you know of any other references that I could be=gin
> >> climbing?
> >> "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com> wrote in message
> >>news:uOzg3KRAIHA.464@.TK2MSFTNGP02.phx.gbl...
> >> Unless you need to I would not go to PDF. RS can render in multiple
> >> ways but PDF and Excel are the slowest. It is not saving the file
> >> anywhere, it is streaming it to you.
> >> You can integrate in two ways, web services or URL integration. If y=ou
> >> use URL integration (the easiest) then the user can get the full
> >> benefit of the server including printing support and they have have
> >> html output as the rendering type which is much much faster than pdf.
> >> In books online the documentation is quite good (RS 2005). If you are
> >> using RS 2000 then go to the MS site and look at the books on line
> >> there for RS 2005. URL integration has not changed between versions.
> >> For example, here is an example URL that sends a parameter. Your app
> >> would just assemble the URL. I strongly recommend starting this way.
> >> Otherwise I see a very large learning curve for you. You need to lea=rn
> >> and understand Reporting Services. With URL integration you can
> >> concentrate on that without worrying about webservices from asp 3.0
> >> website.
> >> Here are some quick examples. I show below different rendering as we=ll:
> >> Excel, PDF and the default HTML.
> >> This renders as Excel
> >>http://servername/reportserver?/Sales/YearlySalesSummary&rs:Format=3D=
Ex...
> >> renders as PDF and passes a parameter for the year
> >>http://servername/reportserver?/Sales/YearlySalesSummary&Year=3D2006&=
rs...
> >> renders as HTML (the speediest) which is the default if nothing is
> >> specified.
> >>http://servername/reportserver?/Sales/YearlySalesSummary&Year=3D2006W=
hen
> >> integrating with older technology URL integration in my mind is the =way
> >> to go.
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >> "Don Miller" <nos...@.nospam.com> wrote in message
> >>news:elTFOiLAIHA.464@.TK2MSFTNGP02.phx.gbl...
> >> Thanks for the pointer.
> >> But how do I specify where the PDF file is created (or is that
> >> hard-coded into the web service?)?
> >> And how would I get back the physical path (including filename) of =the
> >> PDF file?
> >> I'm really new at web services and I realize these questions may be
> >> naive. Thanks again.
> >> "EMartinez" <emartinez...@.gmail.com> wrote in message
> >>news:1190854577.900501.137650@.w3g2000hsg.googlegroups.com...
> >> On Sep 26, 6:51 pm, "Don Miller" <nos...@.nospam.com> wrote:
> >>> I currently use Crystal Reports RDC that is called from an ASP 3.0
> >>> page
> >>> (actually, the ASP page calls my custom VB COM+ code which then
> >>> calls then
> >>> RDC), supplies a CustomerID as a parameter to generate a report
> >>> (e.g. on one
> >>> customer) that is then exported as a PDF file and saved to the
> >>> filesystem on
> >>> the server. That PDF is then available for download by end-users =in
> >>> my web
> >>> application (i.e. as a link). Since the move to Win2003/SQL Server
> >>> 2005 one
> >>> of the Crystal components is misbehaving and I'd like to move this
> >>> report
> >>> entirely to SSRS.
> >>> However, my entire web application is classic ASP 3.0 (and will n=ot
> >>> be
> >>> changing anytime soon). So what I'd like to do is call a web serv=ice
> >>> with a
> >>> parameter from my ASP 3.0 page (e.g. CustomerID), have the web
> >>> service
> >>> generate the report, save the PDF file on the server, and return
> >>> back to the
> >>> ASP page the path to the PDF file. Except I don't know how to do
> >>> this and
> >>> cannot find any examples of using ASP 3.0 with SSRS. I can probab=ly
> >>> do some
> >>> limited ASP.NET 2.0 programming to create the web service but need
> >>> help
> >>> doing that (if necessary).
> >>> Can someone please direct me to examples of how to use ASP 3.0 and
> >>> SSRS
> >>> together? Or tell me if I'm going about it the wrong way (e.g. do= I
> >>> even
> >>> need to save the PDF on the server)?
> >>> Thanks for any help or direction.
> >> You can either iFrame a connection to the Report Server and/or you
> >> can
> >> access a report and export it to a predefined format via URL from
> >> within ASP 3.0. Here's an example of calling a report and exporting
> >> it
> >> to PDF and separately to Excel.
> ...
> read more =BB
Another option, if you can utilize a web service in ASP.NET (which you
eluded to in the beginning) is to use the URL method that both I and
Bruce mentioned and then use a combination of StreamReader and
StreamWriter in ASP.NET (http://msdn2.microsoft.com/en-us/library/
aa903247(VS.71).aspx ) to return the stream from the URL call (via
StreamReader) and then write the file physically out to disk (via
StreamWriter). The report file normally defaults to the 'report name'
+ 'extension of export option selected'; however, you can control the
filename after the fact as well using File.Move in ASP.NET (https://
msdn2.microsoft.com/en-us/library/system.io.file.move.aspx ). Of
course, you would need to know how to reference the Web Service via
SOAP. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Yes, I would like to use the URL method, but what you suggest (and how to do
it) is probably part of the steep learning curve I have not yet approached.
It's probably not so important to me anymore that I continue to write the
PDF to the server as long as the end-user can save it on their local machine
(which they can just using the URL method).
Again, it is still difficult to use SOAP with classic ASP 3.0 (there is
apparently a MS COM object that will no longer be supported in 2008 that
helps) and I'm probably out of my space (mind) to handcraft all of that in
ASP 3.0 to use the Reporting Service API.
Security is a major concern (that I've created another post in this
newsgroup) and I cannot make heads or tails about the issue in BOL.
I appreciate your assistance and expertise.
"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:1190942221.341537.319500@.n39g2000hsh.googlegroups.com...
On Sep 27, 12:12 pm, "Don Miller" <nos...@.nospam.com> wrote:
> After very brief playing, with the complete URL, this may indeed work (and
> save me the trouble of deleting PDFs off the server every night - with a
> BAT
> file ;) BUT I need to have the default filename to be saved to be specific
> when folks save the exported file (see other Topic I've posted).
> It's always something ;)
> "Don Miller" <nos...@.nospam.com> wrote in message
> news:u6ZWUQSAIHA.4592@.TK2MSFTNGP03.phx.gbl...
> > Thanks. I certainly am stuck in the mindset I've had and used
> > successfully
> > for the last seven years. Time to change maybe.
> > Although saving the report as PDF to a device is optional (but
> > necessary),
> > most of my customers click on the link to the PDF file (on the server)
> > on
> > my web page and it loads into Adobe Reader plug-in and they simply print
> > out the PDF document and save *that* paper as their permanent record.
> > So,
> > a "file download" box appearing first would not be a good thing for most
> > customers (but I assume there will be an Open instead option with
> > configuration of the response headers?).
> > I actually do NOT want to expose my customers to the full Report Manager
> > at all or give them options to save the report in any other format. They
> > just want one thing and many of my end-users would be overwhelmed by
> > anything other than "click here" to view the report. These are not
> > business people and many only have high-school diplomas and "variety" is
> > not good.
> > Nevertheless, I'll take your seasoned advice and play around a bit. But
> > with this and all the hacking that has to be done (no Report
> > Headers/Footers without tricks, hidden parameters, no Fields in Page
> > Headers, no tabs, no document size editing, etc.) to recreate a Crystal
> > Reports report, I may be going right back to CR. I hope not though.
> > "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com> wrote in message
> >news:uN2MBBSAIHA.4444@.TK2MSFTNGP03.phx.gbl...
> >> If you use URL integration you get the full Report Manager (the portal
> >> that ships with RS) interface. This allows the user to save as in any
> >> of
> >> the formats. So, they get very fast html for viewing and they can save
> >> as
> >> they want when they want in a variety of formats. IF you pick PDF
> >> (which
> >> the example showed) then what happens is the PDF is viewed in the
> >> browser. They can save or they can export as PDF.
> >> Nothing prevents you from using PDF as your design target. There are
> >> definitely things you can do in PDF that you cannot do in html format.
> >> However, when developing this means you will need to do lots of
> >> deploying
> >> and viewing. The development environment preview is html.
> >> You are a little stuck with how the previous environment worked. RS is
> >> streaming the result back to the browser. The browser is the target.
> >> You
> >> can change the rendering format but it still gets streamed to the
> >> browser
> >> whether it is Excel, PDF, html, image whatever and then IE determines
> >> how
> >> to handle it. PDF will get a File Download box. If you want to save to
> >> disk on the server your app would have to take the stream and write it
> >> to
> >> disk.
> >> You also with URL integration have control over which parts of the
> >> screen
> >> to show, for instance the parameter section. RS comes with the ability
> >> to
> >> export in multiple formats and to print.
> >> My suggestion is that before you go too much further worry about how to
> >> integrate that you first learn about RS. Create a few simple (very
> >> simple) reports. Try creating the URL and just typing it into the
> >> browser. Do different things by modifying the URL. Save your example
> >> URLs
> >> off. Once you know the capabilities of doing this you can decide if you
> >> need to go more extreme and implement web services.
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >> "Don Miller" <nos...@.nospam.com> wrote in message
> >>news:OOkUblRAIHA.3548@.TK2MSFTNGP06.phx.gbl...
> >> Thanks for your time putting this together and your advice.
> >> Unfortunately, I do "need" a PDF as a file that can be downloaded and
> >> saved to device (disk, network share, flash drive, etc.) by my
> >> customers
> >> for their permanent and legal records (I tell them to right-click my
> >> link and "Save Target As..." to do the save, rather than rely on Adobe
> >> Reader Disk Save icon). This is a fundamental business requirement.
> >> Also, the report is usually 8-10 page long and contains about a dozen
> >> sub-reports all with different and intricate formatting that cannot be
> >> duplicated with HTML (even if I wanted to save in that format). And it
> >> does currently takes about 5-10secs to generate (it basically takes
> >> ALL
> >> the information about a customer in the database and exports it).
> >> So, if I understand you, even in the best of circumstances, the
> >> exported
> >> PDF document is not ever saved physically to disk on the server? This
> >> might still work as long as my customer *could* save it with Adobe
> >> Reader in the browser.
> >> Otherwise I see a very large learning curve for you.
> >> Do you know of anyone who has already climbed that mountain who I
> >> could
> >> contract to provide the framework for accessing exported PDF files
> >> from
> >> SSRS from ASP 3.0?
> >> And if you don't, do you know of any other references that I could
> >> begin
> >> climbing?
> >> "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com> wrote in message
> >>news:uOzg3KRAIHA.464@.TK2MSFTNGP02.phx.gbl...
> >> Unless you need to I would not go to PDF. RS can render in multiple
> >> ways but PDF and Excel are the slowest. It is not saving the file
> >> anywhere, it is streaming it to you.
> >> You can integrate in two ways, web services or URL integration. If
> >> you
> >> use URL integration (the easiest) then the user can get the full
> >> benefit of the server including printing support and they have have
> >> html output as the rendering type which is much much faster than pdf.
> >> In books online the documentation is quite good (RS 2005). If you are
> >> using RS 2000 then go to the MS site and look at the books on line
> >> there for RS 2005. URL integration has not changed between versions.
> >> For example, here is an example URL that sends a parameter. Your app
> >> would just assemble the URL. I strongly recommend starting this way.
> >> Otherwise I see a very large learning curve for you. You need to
> >> learn
> >> and understand Reporting Services. With URL integration you can
> >> concentrate on that without worrying about webservices from asp 3.0
> >> website.
> >> Here are some quick examples. I show below different rendering as
> >> well:
> >> Excel, PDF and the default HTML.
> >> This renders as Excel
> >>http://servername/reportserver?/Sales/YearlySalesSummary&rs:Format=Ex...
> >> renders as PDF and passes a parameter for the year
> >>http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006&rs...
> >> renders as HTML (the speediest) which is the default if nothing is
> >> specified.
> >>http://servername/reportserver?/Sales/YearlySalesSummary&Year=2006When
> >> integrating with older technology URL integration in my mind is the
> >> way
> >> to go.
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >> "Don Miller" <nos...@.nospam.com> wrote in message
> >>news:elTFOiLAIHA.464@.TK2MSFTNGP02.phx.gbl...
> >> Thanks for the pointer.
> >> But how do I specify where the PDF file is created (or is that
> >> hard-coded into the web service?)?
> >> And how would I get back the physical path (including filename) of
> >> the
> >> PDF file?
> >> I'm really new at web services and I realize these questions may be
> >> naive. Thanks again.
> >> "EMartinez" <emartinez...@.gmail.com> wrote in message
> >>news:1190854577.900501.137650@.w3g2000hsg.googlegroups.com...
> >> On Sep 26, 6:51 pm, "Don Miller" <nos...@.nospam.com> wrote:
> >>> I currently use Crystal Reports RDC that is called from an ASP 3.0
> >>> page
> >>> (actually, the ASP page calls my custom VB COM+ code which then
> >>> calls then
> >>> RDC), supplies a CustomerID as a parameter to generate a report
> >>> (e.g. on one
> >>> customer) that is then exported as a PDF file and saved to the
> >>> filesystem on
> >>> the server. That PDF is then available for download by end-users
> >>> in
> >>> my web
> >>> application (i.e. as a link). Since the move to Win2003/SQL Server
> >>> 2005 one
> >>> of the Crystal components is misbehaving and I'd like to move this
> >>> report
> >>> entirely to SSRS.
> >>> However, my entire web application is classic ASP 3.0 (and will
> >>> not
> >>> be
> >>> changing anytime soon). So what I'd like to do is call a web
> >>> service
> >>> with a
> >>> parameter from my ASP 3.0 page (e.g. CustomerID), have the web
> >>> service
> >>> generate the report, save the PDF file on the server, and return
> >>> back to the
> >>> ASP page the path to the PDF file. Except I don't know how to do
> >>> this and
> >>> cannot find any examples of using ASP 3.0 with SSRS. I can
> >>> probably
> >>> do some
> >>> limited ASP.NET 2.0 programming to create the web service but need
> >>> help
> >>> doing that (if necessary).
> >>> Can someone please direct me to examples of how to use ASP 3.0 and
> >>> SSRS
> >>> together? Or tell me if I'm going about it the wrong way (e.g. do
> >>> I
> >>> even
> >>> need to save the PDF on the server)?
> >>> Thanks for any help or direction.
> >> You can either iFrame a connection to the Report Server and/or you
> >> can
> >> access a report and export it to a predefined format via URL from
> >> within ASP 3.0. Here's an example of calling a report and exporting
> >> it
> >> to PDF and separately to Excel.
> ...
> read more »
Another option, if you can utilize a web service in ASP.NET (which you
eluded to in the beginning) is to use the URL method that both I and
Bruce mentioned and then use a combination of StreamReader and
StreamWriter in ASP.NET (http://msdn2.microsoft.com/en-us/library/
aa903247(VS.71).aspx ) to return the stream from the URL call (via
StreamReader) and then write the file physically out to disk (via
StreamWriter). The report file normally defaults to the 'report name'
+ 'extension of export option selected'; however, you can control the
filename after the fact as well using File.Move in ASP.NET (https://
msdn2.microsoft.com/en-us/library/system.io.file.move.aspx ). Of
course, you would need to know how to reference the Web Service via
SOAP. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||On Sep 28, 7:37 am, "Don Miller" <nos...@.nospam.com> wrote:
> Yes, I would like to use the URL method, but what you suggest (and how to= do
> it) is probably part of the steep learning curve I have not yet approache=d=2E
> It's probably not so important to me anymore that I continue to write the
> PDF to the server as long as the end-user can save it on their local mach=ine
> (which they can just using the URL method).
> Again, it is still difficult to use SOAP with classic ASP 3.0 (there is
> apparently a MS COM object that will no longer be supported in 2008 that
> helps) and I'm probably out of my space (mind) to handcraft all of that in
> ASP 3.0 to use the Reporting Service API.
> Security is a major concern (that I've created another post in this
> newsgroup) and I cannot make heads or tails about the issue in BOL.
> I appreciate your assistance and expertise.
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:1190942221.341537.319500@.n39g2000hsh.googlegroups.com...
> On Sep 27, 12:12 pm, "Don Miller" <nos...@.nospam.com> wrote:
> > After very brief playing, with the complete URL, this may indeed work (=and
> > save me the trouble of deleting PDFs off the server every night - with a
> > BAT
> > file ;) BUT I need to have the default filename to be saved to be speci=fic
> > when folks save the exported file (see other Topic I've posted).
> > It's always something ;)
> > "Don Miller" <nos...@.nospam.com> wrote in message
> >news:u6ZWUQSAIHA.4592@.TK2MSFTNGP03.phx.gbl...
> > > Thanks. I certainly am stuck in the mindset I've had and used
> > > successfully
> > > for the last seven years. Time to change maybe.
> > > Although saving the report as PDF to a device is optional (but
> > > necessary),
> > > most of my customers click on the link to the PDF file (on the server)
> > > on
> > > my web page and it loads into Adobe Reader plug-in and they simply pr=int
> > > out the PDF document and save *that* paper as their permanent record.
> > > So,
> > > a "file download" box appearing first would not be a good thing for m=ost
> > > customers (but I assume there will be an Open instead option with
> > > configuration of the response headers?).
> > > I actually do NOT want to expose my customers to the full Report Mana=ger
> > > at all or give them options to save the report in any other format. T=hey
> > > just want one thing and many of my end-users would be overwhelmed by
> > > anything other than "click here" to view the report. These are not
> > > business people and many only have high-school diplomas and "variety"= is
> > > not good.
> > > Nevertheless, I'll take your seasoned advice and play around a bit. B=ut
> > > with this and all the hacking that has to be done (no Report
> > > Headers/Footers without tricks, hidden parameters, no Fields in Page
> > > Headers, no tabs, no document size editing, etc.) to recreate a Cryst=al
> > > Reports report, I may be going right back to CR. I hope not though.
> > > "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com> wrote in message
> > >news:uN2MBBSAIHA.4444@.TK2MSFTNGP03.phx.gbl...
> > >> If you use URL integration you get the full Report Manager (the port=al
> > >> that ships with RS) interface. This allows the user to save as in any
> > >> of
> > >> the formats. So, they get very fast html for viewing and they can sa=ve
> > >> as
> > >> they want when they want in a variety of formats. IF you pick PDF
> > >> (which
> > >> the example showed) then what happens is the PDF is viewed in the
> > >> browser. They can save or they can export as PDF.
> > >> Nothing prevents you from using PDF as your design target. There are
> > >> definitely things you can do in PDF that you cannot do in html forma=t=2E
> > >> However, when developing this means you will need to do lots of
> > >> deploying
> > >> and viewing. The development environment preview is html.
> > >> You are a little stuck with how the previous environment worked. RS =is
> > >> streaming the result back to the browser. The browser is the target.
> > >> You
> > >> can change the rendering format but it still gets streamed to the
> > >> browser
> > >> whether it is Excel, PDF, html, image whatever and then IE determines
> > >> how
> > >> to handle it. PDF will get a File Download box. If you want to save= to
> > >> disk on the server your app would have to take the stream and write =it
> > >> to
> > >> disk.
> > >> You also with URL integration have control over which parts of the
> > >> screen
> > >> to show, for instance the parameter section. RS comes with the abili=ty
> > >> to
> > >> export in multiple formats and to print.
> > >> My suggestion is that before you go too much further worry about how= to
> > >> integrate that you first learn about RS. Create a few simple (very
> > >> simple) reports. Try creating the URL and just typing it into the
> > >> browser. Do different things by modifying the URL. Save your example
> > >> URLs
> > >> off. Once you know the capabilities of doing this you can decide if =you
> > >> need to go more extreme and implement web services.
> > >> --
> > >> Bruce Loehle-Conger
> > >> MVP SQL Server Reporting Services
> > >> "Don Miller" <nos...@.nospam.com> wrote in message
> > >>news:OOkUblRAIHA.3548@.TK2MSFTNGP06.phx.gbl...
> > >> Thanks for your time putting this together and your advice.
> > >> Unfortunately, I do "need" a PDF as a file that can be downloaded a=nd
> > >> saved to device (disk, network share, flash drive, etc.) by my
> > >> customers
> > >> for their permanent and legal records (I tell them to right-click my
> > >> link and "Save Target As..." to do the save, rather than rely on Ad=obe
> > >> Reader Disk Save icon). This is a fundamental business requirement.
> > >> Also, the report is usually 8-10 page long and contains about a doz=en
> > >> sub-reports all with different and intricate formatting that cannot= be
> > >> duplicated with HTML (even if I wanted to save in that format). And= it
> > >> does currently takes about 5-10secs to generate (it basically takes
> > >> ALL
> > >> the information about a customer in the database and exports it).
> > >> So, if I understand you, even in the best of circumstances, the
> > >> exported
> > >> PDF document is not ever saved physically to disk on the server? Th=is
> > >> might still work as long as my customer *could* save it with Adobe
> > >> Reader in the browser.
> > >> Otherwise I see a very large learning curve for you.
> > >> Do you know of anyone who has already climbed that mountain who I
> > >> could
> > >> contract to provide the framework for accessing exported PDF files
> > >> from
> > >> SSRS from ASP 3.0?
> > >> And if you don't, do you know of any other references that I could
> > >> begin
> > >> climbing?
> > >> "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com> wrote in message
> > >>news:uOzg3KRAIHA.464@.TK2MSFTNGP02.phx.gbl...
> > >> Unless you need to I would not go to PDF. RS can render in multiple
> > >> ways but PDF and Excel are the slowest. It is not saving the file
> > >> anywhere, it is streaming it to you.
> > >> You can integrate in two ways, web services or URL integration. If
> > >> you
> > >> use URL integration (the easiest) then the user can get the full
> > >> benefit of the server including printing support and they have have
> > >> html output as the rendering type which is much much faster than p=df.
> > >> In books online the documentation is quite good (RS 2005). If you =are
> > >> using RS 2000 then go to the MS site and look at the books on line
> > >> there for RS 2005. URL integration has not changed between version=s=2E
> > >> For example, here is an example URL that sends a parameter. Your a=pp
> > >> would just assemble the URL. I strongly recommend starting this wa=y=2E
> > >> Otherwise I see a very large learning curve for you. You need to
> > >> learn
> > >> and understand Reporting Services. With URL integration you can
> > >> concentrate on that without worrying about webservices from asp 3.0
> > >> website.
> > >> Here are some quick examples. I show below different rendering as
> > >> well:
> > >> Excel, PDF and the default HTML.
> > >> This renders as Excel
> > >>http://servername/reportserver?/Sales/YearlySalesSummary&rs:Format=
=3DEx...
> > >> renders as PDF and passes a parameter for the year
> > >>http://servername/reportserver?/Sales/YearlySalesSummary&Year=3D200=
6&rs...
> > >> renders as HTML (the speediest) which is the default if nothing is
> > >> specified.
> > >>http://servername/reportserver?/Sales/YearlySalesSummary&Year=3D200=
6When
> > >> integrating with older technology URL integration in my mind is the
> > >> way
> > >> to go.
> > >> --
> > >> Bruce Loehle-Conger
> > >> MVP SQL Server Reporting Services
> > >> "Don Miller" <nos...@.nospam.com> wrote in message
> > >>news:elTFOiLAIHA.464@.TK2MSFTNGP02.phx.gbl...
> > >> Thanks for the pointer.
> > >> But how do I specify where the PDF file is created (or is that
> > >> hard-coded into the web service?)?
> > >> And how would I get back the physical path (including filename) of
> > >> the
> > >> PDF file?
> > >> I'm really new at web services and I realize these questions may =be
> > >> naive. Thanks again.
> > >> "EMartinez" <emartinez...@.gmail.com> wrote in message
> > >>news:1190854577.900501.137650@.w3g2000hsg.googlegroups.com...
> > >> On Sep 26, 6:51 pm, "Don Miller" <nos...@.nospam.com> wrote:
> > >>> I currently use Crystal Reports RDC that is called from an ASP =3=2E0
> > >>> page
> > >>> (actually, the ASP page calls my custom VB COM+ code which then
> > >>> calls then
> > >>> RDC), supplies a CustomerID as a parameter to generate a report
> > >>> (e.g. on one
> > >>> customer) that is then exported as a PDF file and saved to the
> > >>> filesystem on
> > >>> the server. That PDF is then available for download by end-users
> > >>> in
> > >>> my web
> > >>> application (i.e. as a link). Since the move to Win2003/SQL Ser=ver
> > >>> 2005 one
> > >>> of the Crystal components is misbehaving and I'd like to move t=his
> > >>> report
> > >>> entirely to SSRS.
> > >>> However, my entire web application is classic ASP 3.0 (and will
> > >>> not
> > >>> be
> > >>> changing anytime soon). So what I'd like to do is call a web
> > >>> service
> > >>> with a
> > >>> parameter from my ASP 3.0 page (e.g. CustomerID), have the web
> > >>> service
> > >>> generate the report, save the PDF file on the server, and return
> > >>> back to the
> > >>> ASP page the path to the PDF file. Except I don't know how to do
> > >>> this and
> > >>> cannot find any examples of using ASP 3.0 with SSRS. I can
> > >>> probably
> > >>> do some
> > >>> limited ASP.NET 2.0 programming to create the web service but n=eed
> > >>> help
> > >>> doing that (if necessary).
> > >>> Can someone please direct me to examples of how to use ASP 3.0 =and
> > >>> SSRS
> > >>> together? Or tell me if I'm going about it the wrong way (e.g. =do
> > >>> I
> > >>> even
> > >>> need to save the PDF on the server)?
> > >>> Thanks for any help or direction.
> > >> You can either iFrame a connection to the Report Server and/or y=ou
> > >> can
> > >> access a report and export it to a predefined format via URL from
> > >> within ASP 3.0. Here's an example of calling a report and export=ing
> > >> it
> > >> to PDF and separately to Excel.
> > ...
> > read more =BB
> Another option, if you can utilize a web service in ASP.NET (which you
> eluded to in the beginning) is to use the URL method that both I and
> Bruce mentioned and then use a combination of StreamReader and
> StreamWriter in ASP.NET (http://msdn2.microsoft.com/en-us/library/
> aa903247(VS.71).aspx ) to return the stream from the URL call (via
> StreamReader) and then write the file physically out to disk (via
> StreamWriter). The report file normally defaults to the 'report name'
> + 'extension of export option selected'; however, you can control the
> filename after the fact as well using File.Move in ASP.NET (https://
> msdn2.microsoft.com/en-us/library/system.io.file.move.aspx ). Of
> course, you would need to know how to reference the Web Service via
> SOAP. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Well, if you need further assistance, let me know. The web service
solution I mentioned early is pretty quick and doesn't take much
coding.
Regards,
Enrique Martinez
Sr. Software Consultant|||Hi Don
I was wondring if you can help me with this . I have created
crystal reports(crystal developer edition) in widows 2000 server and calling
via ASP using RDC.
No i need to insall it on production server. I registered all the DLLS given
by BO. does not work.
can you help
shireesh
shireeshkumar@.ups.com
"Don Miller" wrote:
> I currently use Crystal Reports RDC that is called from an ASP 3.0 page
> (actually, the ASP page calls my custom VB COM+ code which then calls then
> RDC), supplies a CustomerID as a parameter to generate a report (e.g. on one
> customer) that is then exported as a PDF file and saved to the filesystem on
> the server. That PDF is then available for download by end-users in my web
> application (i.e. as a link). Since the move to Win2003/SQL Server 2005 one
> of the Crystal components is misbehaving and I'd like to move this report
> entirely to SSRS.
> However, my entire web application is classic ASP 3.0 (and will not be
> changing anytime soon). So what I'd like to do is call a web service with a
> parameter from my ASP 3.0 page (e.g. CustomerID), have the web service
> generate the report, save the PDF file on the server, and return back to the
> ASP page the path to the PDF file. Except I don't know how to do this and
> cannot find any examples of using ASP 3.0 with SSRS. I can probably do some
> limited ASP.NET 2.0 programming to create the web service but need help
> doing that (if necessary).
> Can someone please direct me to examples of how to use ASP 3.0 and SSRS
> together? Or tell me if I'm going about it the wrong way (e.g. do I even
> need to save the PDF on the server)?
> Thanks for any help or direction.
>
>|||I only have worked with RDC 8.5 and I know how to get that to work for
exporting PDFs only (with only 5 or 6 DLLs). I recently tried to use RDC XI
and could not get it to work (CR only supports installation of ALL of their
associated DLLs - 150mbs worth - using the installation package - they do
not support picking, choosing, and registering individual DLLs).
So, what version are you working with?
"shireesh" <shireesh@.discussions.microsoft.com> wrote in message
news:852587F4-3028-4F36-8851-57C8DC559B7A@.microsoft.com...
> Hi Don
> I was wondring if you can help me with this . I have created
> crystal reports(crystal developer edition) in widows 2000 server and
> calling
> via ASP using RDC.
> No i need to insall it on production server. I registered all the DLLS
> given
> by BO. does not work.
> can you help
> shireesh
> shireeshkumar@.ups.com
> "Don Miller" wrote:
>> I currently use Crystal Reports RDC that is called from an ASP 3.0 page
>> (actually, the ASP page calls my custom VB COM+ code which then calls
>> then
>> RDC), supplies a CustomerID as a parameter to generate a report (e.g. on
>> one
>> customer) that is then exported as a PDF file and saved to the filesystem
>> on
>> the server. That PDF is then available for download by end-users in my
>> web
>> application (i.e. as a link). Since the move to Win2003/SQL Server 2005
>> one
>> of the Crystal components is misbehaving and I'd like to move this report
>> entirely to SSRS.
>> However, my entire web application is classic ASP 3.0 (and will not be
>> changing anytime soon). So what I'd like to do is call a web service with
>> a
>> parameter from my ASP 3.0 page (e.g. CustomerID), have the web service
>> generate the report, save the PDF file on the server, and return back to
>> the
>> ASP page the path to the PDF file. Except I don't know how to do this and
>> cannot find any examples of using ASP 3.0 with SSRS. I can probably do
>> some
>> limited ASP.NET 2.0 programming to create the web service but need help
>> doing that (if necessary).
>> Can someone please direct me to examples of how to use ASP 3.0 and SSRS
>> together? Or tell me if I'm going about it the wrong way (e.g. do I even
>> need to save the PDF on the server)?
>> Thanks for any help or direction.
>>|||Hi Don
Thanks for the reply . I am using Crystal 8.5 . i used the
following DLLs
Craxdrt.dll,CRViewer.dll,CRdesigner.dll,CRDesignerCtrl.dll,CRaxddrt.dll,p2soledb.ddl,p2sodbc.dll.
I see no error just balnk white screen.
My envrionment is
Microsoft 2000 server SP4
Sqlserver 2000 SP4
Crystal Reports 8.5
ASP
I am using stored procedure for Crytal reports
Please help if i am missign something.
thanks
shireesh
"Don Miller" wrote:
> I only have worked with RDC 8.5 and I know how to get that to work for
> exporting PDFs only (with only 5 or 6 DLLs). I recently tried to use RDC XI
> and could not get it to work (CR only supports installation of ALL of their
> associated DLLs - 150mbs worth - using the installation package - they do
> not support picking, choosing, and registering individual DLLs).
> So, what version are you working with?
>
> "shireesh" <shireesh@.discussions.microsoft.com> wrote in message
> news:852587F4-3028-4F36-8851-57C8DC559B7A@.microsoft.com...
> > Hi Don
> > I was wondring if you can help me with this . I have created
> > crystal reports(crystal developer edition) in widows 2000 server and
> > calling
> > via ASP using RDC.
> > No i need to insall it on production server. I registered all the DLLS
> > given
> > by BO. does not work.
> >
> > can you help
> >
> > shireesh
> > shireeshkumar@.ups.com
> >
> > "Don Miller" wrote:
> >
> >> I currently use Crystal Reports RDC that is called from an ASP 3.0 page
> >> (actually, the ASP page calls my custom VB COM+ code which then calls
> >> then
> >> RDC), supplies a CustomerID as a parameter to generate a report (e.g. on
> >> one
> >> customer) that is then exported as a PDF file and saved to the filesystem
> >> on
> >> the server. That PDF is then available for download by end-users in my
> >> web
> >> application (i.e. as a link). Since the move to Win2003/SQL Server 2005
> >> one
> >> of the Crystal components is misbehaving and I'd like to move this report
> >> entirely to SSRS.
> >>
> >> However, my entire web application is classic ASP 3.0 (and will not be
> >> changing anytime soon). So what I'd like to do is call a web service with
> >> a
> >> parameter from my ASP 3.0 page (e.g. CustomerID), have the web service
> >> generate the report, save the PDF file on the server, and return back to
> >> the
> >> ASP page the path to the PDF file. Except I don't know how to do this and
> >> cannot find any examples of using ASP 3.0 with SSRS. I can probably do
> >> some
> >> limited ASP.NET 2.0 programming to create the web service but need help
> >> doing that (if necessary).
> >>
> >> Can someone please direct me to examples of how to use ASP 3.0 and SSRS
> >> together? Or tell me if I'm going about it the wrong way (e.g. do I even
> >> need to save the PDF on the server)?
> >>
> >> Thanks for any help or direction.
> >>
> >>
> >>
>
>|||For my requirements (load a report and export it as PDF to my server's file
system using OLEDB for data access) it requires that I put crxf_pdf.dll,
p2soledb.dll, and u2ddisk.dll in a folder called Crystal in either WINDOWS
or WINNT folder. The files in this folder do NOT need to be registered (you
can't anyway).
The other critical files go in some folder of your choice but all need to be
registered. This includes craxdrt.dll, crtslv.dll, and ExportModeller.dll
(for my implementation).
So I suspect you need to put p2soledb.ddl, p2sodbc.dll in a folder named
Crystal in WINNT and the others in a folder of your choice and register them
all with the system. I don't use those other DLLs so I don't really know
where they go.
I hope this helps a little.
"shireesh" <shireesh@.discussions.microsoft.com> wrote in message
news:82337A68-166D-4E96-9B76-B98F44214736@.microsoft.com...
> Hi Don
> Thanks for the reply . I am using Crystal 8.5 . i used the
> following DLLs
> Craxdrt.dll,CRViewer.dll,CRdesigner.dll,CRDesignerCtrl.dll,CRaxddrt.dll,p2soledb.ddl,p2sodbc.dll.
> I see no error just balnk white screen.
> My envrionment is
> Microsoft 2000 server SP4
> Sqlserver 2000 SP4
> Crystal Reports 8.5
> ASP
> I am using stored procedure for Crytal reports
> Please help if i am missign something.
> thanks
> shireesh
>
> "Don Miller" wrote:
>> I only have worked with RDC 8.5 and I know how to get that to work for
>> exporting PDFs only (with only 5 or 6 DLLs). I recently tried to use RDC
>> XI
>> and could not get it to work (CR only supports installation of ALL of
>> their
>> associated DLLs - 150mbs worth - using the installation package - they do
>> not support picking, choosing, and registering individual DLLs).
>> So, what version are you working with?
>>
>> "shireesh" <shireesh@.discussions.microsoft.com> wrote in message
>> news:852587F4-3028-4F36-8851-57C8DC559B7A@.microsoft.com...
>> > Hi Don
>> > I was wondring if you can help me with this . I have created
>> > crystal reports(crystal developer edition) in widows 2000 server and
>> > calling
>> > via ASP using RDC.
>> > No i need to insall it on production server. I registered all the DLLS
>> > given
>> > by BO. does not work.
>> >
>> > can you help
>> >
>> > shireesh
>> > shireeshkumar@.ups.com
>> >
>> > "Don Miller" wrote:
>> >
>> >> I currently use Crystal Reports RDC that is called from an ASP 3.0
>> >> page
>> >> (actually, the ASP page calls my custom VB COM+ code which then calls
>> >> then
>> >> RDC), supplies a CustomerID as a parameter to generate a report (e.g.
>> >> on
>> >> one
>> >> customer) that is then exported as a PDF file and saved to the
>> >> filesystem
>> >> on
>> >> the server. That PDF is then available for download by end-users in my
>> >> web
>> >> application (i.e. as a link). Since the move to Win2003/SQL Server
>> >> 2005
>> >> one
>> >> of the Crystal components is misbehaving and I'd like to move this
>> >> report
>> >> entirely to SSRS.
>> >>
>> >> However, my entire web application is classic ASP 3.0 (and will not be
>> >> changing anytime soon). So what I'd like to do is call a web service
>> >> with
>> >> a
>> >> parameter from my ASP 3.0 page (e.g. CustomerID), have the web service
>> >> generate the report, save the PDF file on the server, and return back
>> >> to
>> >> the
>> >> ASP page the path to the PDF file. Except I don't know how to do this
>> >> and
>> >> cannot find any examples of using ASP 3.0 with SSRS. I can probably do
>> >> some
>> >> limited ASP.NET 2.0 programming to create the web service but need
>> >> help
>> >> doing that (if necessary).
>> >>
>> >> Can someone please direct me to examples of how to use ASP 3.0 and
>> >> SSRS
>> >> together? Or tell me if I'm going about it the wrong way (e.g. do I
>> >> even
>> >> need to save the PDF on the server)?
>> >>
>> >> Thanks for any help or direction.
>> >>
>> >>
>> >>
>>