On Mar 30, 9:17 am, "Stan Spotts" <sspo...@community.nospam> wrote:
> I don't even _have_ VS 6.0 on a machine anywhere, so I can't muck around
> with it, so I'm hoping someone can supply sample code and/or links to
> examples or other info that can show how to execute a report from "Classic"
> ASP (not .NET). We have some legacy apps that aren't being migrated to .NET
> and are being maintained off-shore, but want to get Crystal Reports out of
> the picture.
>
> Any help will be appreciated.
>
> Thanks,
> --Stan

"Steven Cheng[MSFT]" <stcheng@online.microsoft.com> wrote in message
news:otVgSQPdHHA.6068@TK2MSFTNGHUB02.phx.gbl...
> Hi Stan,
>
> For your classic ASP application, is it an public internet application or
> for intranet only? As for SQL Server reporting service, if your classic
> ASP application's client user can also directly access the reporting
> service server, you can directly use "URL ACCESS" to let your asp page
> redirect client user to the report server url so as to view the report.
> Here is the BOL reference discussing on this:
>
> #SQL Server 2005 Books Online Using URL Access in a Web Application
> http://msdn2.microsoft.com/en-us/library/ms153563.aspx
>
> If the SSRS report server is not able to directly access by client user(of
> the classic ASP app), I think you can consider the following approach:
>
> ** develop a separate ASP.NET web application(a simple .NET application or
> component) which access the reporting service webservice and output a
> certain report as image or other binary stream.
>
> ** your classic ASP page communicate with that .NET based application to
> query the binary content of the report and expose it to the end user.
>
> How do you think? Please feel free to post here if you have any further
> concerns.
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
>
> ==================================================
>
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
>
>
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
>
> ==================================================
>
>
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
>
>
>
>
>

"Stan Spotts" wrote:

> Steven - thanks, we actually did resort to using url access. I'm not sure
> why the developers went that way rather than figurung out how to call the
> web services and having it send back HTML, etc., but it was the quick and
> dirty way that worked.
>
> Thanks,
> --Stan
>
> "Steven Cheng[MSFT]" <stcheng@online.microsoft.com> wrote in message
> news:otVgSQPdHHA.6068@TK2MSFTNGHUB02.phx.gbl...
> > Hi Stan,
> >
> > For your classic ASP application, is it an public internet application or
> > for intranet only? As for SQL Server reporting service, if your classic
> > ASP application's client user can also directly access the reporting
> > service server, you can directly use "URL ACCESS" to let your asp page
> > redirect client user to the report server url so as to view the report.
> > Here is the BOL reference discussing on this:
> >
> > #SQL Server 2005 Books Online Using URL Access in a Web Application
> > http://msdn2.microsoft.com/en-us/library/ms153563.aspx
> >
> > If the SSRS report server is not able to directly access by client user(of
> > the classic ASP app), I think you can consider the following approach:
> >
> > ** develop a separate ASP.NET web application(a simple .NET application or
> > component) which access the reporting service webservice and output a
> > certain report as image or other binary stream.
> >
> > ** your classic ASP page communicate with that .NET based application to
> > query the binary content of the report and expose it to the end user.
> >
> > How do you think? Please feel free to post here if you have any further
> > concerns.
> >
> > Sincerely,
> >
> > Steven Cheng
> >
> > Microsoft MSDN Online Support Lead
> >
> >
> >
> > ==================================================
> >
> > Get notification to my posts through email? Please refer to
> > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> > ications.
> >
> >
> >
> > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> > where an initial response from the community or a Microsoft Support
> > Engineer within 1 business day is acceptable. Please note that each follow
> > up response may take approximately 2 business days as the support
> > professional working with you may need further investigation to reach the
> > most efficient resolution. The offering is not appropriate for situations
> > that require urgent, real-time or phone-based interactions or complex
> > project analysis and dump analysis issues. Issues of this nature are best
> > handled working with a dedicated Microsoft Support Engineer by contacting
> > Microsoft Customer Support Services (CSS) at
> > http://msdn.microsoft.com/subscriptions/support/default.aspx.
> >
> > ==================================================
> >
> >
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
> >
> >
> >
> >
> >
> >
> >
>
>