executing two designer programs sequentially
terry terry
ggjos@hotmail.com
Wed, 02 Jun 2004 16:12:20 +0000
Hi bob,
First of all , how this works is that the 88 procedure is run then
the screen is cleared and the data is recalled .Secondly the 89 procedure is
then run and the screen is manually updated as in
"U" and return.When done this way every thing works well.I decided to
arrange things in such a way that the 2 procedures would run sequentially ,
instead of 88 recall data ,then 89, I wanted
one action to execute both procedures and save the user needless actions.
Thats when I began having problems.88 generates date-benefit-started which
is needed for 89 to calculate the numbers of days for the claim.As I said,
if the procedures are run separately they work well as long as the screen is
cleared after 88, and the data is retrieved and 89 is then run.But 89 wont
run without retrieving the data on screen after 88 is run . I tried using a
quiz in front of 89 to report on the screen what data was missing when the
88 procedure is run and the date-benefit-started is left
out which is needed for 89. I used your example but the 88 commands keep
running last after the 89. That is when I type "88/89" in the action field
of the screen to have both procedures run sequentially ie 88 then 89.I
switched the order in the DOIT push procedure and 88 still runs last after
89.
>Okay. There are a number of issues here. First of all, you have both PUSH
>UPDATE and PUSH UPDATE STAY in 88. The result of this will be that AFTER
>the execution of 88 completes, QUICK will do an Update (U), followed by an
>Update Stay (US). Depending on the context QUICK is in (data or action)
>after the Update, you may get an error or unexpected results, possibly not
>even noticeable.
>
_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
http://join.msn.com/?page=features/virus