I wouldn't care if the first report wasn't a update report and that the
second one is depending on the results of the first one.
It's thus mandatory to get the 1st one finalized before the 2nd one to be
launched.
"Ed Prochak" <edprochak_at_adelphia.net> wrote in message
news:3EE13918.9010108_at_adelphia.net...
> Guy Van Rinsveld wrote:
> > Hi,
> > How to keep the sequence ordered launching 2 differents concurrent
> > requests (containing both reports) ?
> > The registration of those concurrent requests have been done by
adding
> > incompatibilities between each other and with themselves.
> > It's a script in a form which is launching both reports one after
the
> > other.
> > Hoping that the order of resulting concurrent request ids would be
used
> > for the execution timing sequence.
> > But it's not always the case.
> > 11.5.8 is the level used.
> >
> >
>
> Why do you care? reports shouldn't interfere with each other. So what
really
> is your problem?
>
>
> --
> Ed Prochak
> running http://www.faqs.org/faqs/running-faq/
> netiquette http://www.psg.com/emily.html
> --
> "Two roads diverged in a wood and I
> I took the one less travelled by
> and that has made all the difference."
> robert frost
>
Received on Sat Jun 07 2003 - 10:41:30 CDT
