Re: Reports with more than 2 destinations
Date: Thu, 25 Apr 2002 22:58:36 +0100
Message-ID: <3cc87bef_1_at_news.greennet.net>
I think the point the original poster was that he does not want to query twice.
Imagine my scenario, processing done beforehand ONCE where results stored in temp table. Query takes 2 hours and you run 2 reports based on result set in the temp table
Your way, although feasible will still require 2 queries of 2 hours each, adding up to 4 hours.
Mark
"FC" <flavio_at_tin.it> wrote in message
news:F6Ux8.61285$vF6.1889973_at_news2.tin.it...
>
> Well, that sounds a bit too overengineered, doesn't it?
> Why not letting the report tool do most of the job for you ?
> If the second destination is always a PDF file, I'd suggest to put the
> SRW.RUN_REPORT call within a trigger firing at the end of the report, (or
at
> the beginning, depending on what you prefer to do first or on some other
> constraints).
> In this fashion you still have one report call that kicks off the second
one
> automatically.
>
> The good news is that most of the run time parameters should already be
> there, you'll need to change only the destination name, type, format and
> other minor details perhaps.
> You might also want to consider sending the PDF report to a different
server
> queue if using a report server, so that you don't put too much burden on
the
> same engine, but this will apply only if you install the report server
> component.
> If you are using the report server, be aware that any file paths you
specify
> will refer to the server, not the client!
>
> For further info, you could check page 109 of the Reports Reference Manual
> (A73174_01) where there are some high-level suggestions regarding the
> possible implementations of this procedure.
>
> Bye,
> Flavio
>
>
>
> "Mark" <markg_at_mymail.co.uk> wrote in message
> news:ddb31653.0204250520.215038c7_at_posting.google.com...
> > Nope, a second run of the report is required. The second time around,
> > you will have to change the value of DESTYPE.
> >
> > Alternatively, you can have a form which calls the report. The
> > processing is done and the results stored in a temp table. Then just
> > call the report twice, once for each destination. That way, the main
> > processing is done only.
> >
> > When done, remove contents of temp table.
> >
> > Mark
> >
>
>
>
Received on Thu Apr 25 2002 - 23:58:36 CEST