"//"
Rob Lobbe
rlobbe@vic.bigpond.net.au
Tue, 21 Sep 1999 15:16:27 +1000
Try using a DESIGNER procedure and the PUSH option
PROCEDURE ENTRY
BEGIN
PUSH xyz
ACCEPT field_1
...
ACCEPT field_n
END
PROCEDURE DESIGNER xyz
BEGIN
RUN SCREEN must_run.qkc PASSING ...
END
Note that the PUSH, although being the first command, is executed at the end
of the procedure. So if the "//" option is used, the remaining FIELDs are
SKIPped, however the next COMMAND (ie the PUSH) is executed as it is on the
command stack..
I believe the option was to run a screen after entering "//" to finish entry
and perform some calculations, I'd deleted the original post.
Not quite sure how this works in a CLUSTER, if it runs the command for the
current occurrence then stops, or will run the command for this and each
subsequent occurence (I think not in the latter case)
Rob Lobbe
rlobbe@vic.bigpond.net.au
Practice Manager
Praxa Ltd
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.