By the way... Just how was the control designed to work? Since it accepts the
report name, parameters, server, etc, I made the assumption that client
printing could be accomplished through the use of the control alone.
--
Thanks,
CGW
[quoted text, click to view] "Brian Welcker [MSFT]" wrote:
> The control was not designed to work in this way. You will need to call the
> SOAP APIs.
>
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "CGW" <CGW@discussions.microsoft.com> wrote in message
> news:3E3F8389-4525-4130-A47A-76592F22E643@microsoft.com...
> > After working with this a little more, I believe the problem occurs when
> > RSClientPrint.Print method is invoked for a report without that report
> > being
> > opened first in the browser. I was hoping to bypass that, but
> > RSClientPrint
> > doesn't seem inclined to allow that. Bummer.
> > --
> > Thanks,
> >
> > CGW
> >
> >
> > "CGW" wrote:
> >
> >> I thought I finally had everything in place to do clienside printing
> >> using
> >> RSClientPrint. I even got the dialog box for installing the software at
> >> the
> >> client. However, now when I call my java function to print, I get a error
> >> printing number of 0x8007F304.
> >>
> >> Does anyone recognize it? Can anyone help?
> >>
> >> --
> >> Thanks,
> >>
> >> CGW
>
>