Calling a window from catalyst need to ignore post processes (AREV Specific) [Revelation On-Line Wiki]

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

Calling a window from catalyst need to ignore post processes (AREV Specific)

At 23 DEC 2003 02:35:15PM Mark Watford wrote:

AREV Specific

Using Arev 1.16. Have a program where a window is called from a catalyst command, after this window is opened the user has the ability to change data in the window which has been entered through the program, the user must hit F9 to save the data in the window and after hitting escape it returns to the program which opened the window. This all works fine. Now I have the need to open this window from a Menu, enter data and when saving the record I need a post process to run a subroutine. The problem is that with the first program when the user hits F9 it will run the program from the post process. How could I disable the post process if the window is opened from a Catalyst command not a Menu. Any suggestions would be appreciated

Thanks,

Mark

At 23 DEC 2003 03:35PM matt sorrell wrote:

Mark,

Let's see if I understand this correctly:

Scenario 1: A program is run, which calls the window using a catalyst command. The post-save process should not run in this instance.

Scenario 2: The window is called directly from the menu, with no intervening program being executed. The post-save process should run in this instance.

Using this understanding, here is what I propose. If you are not using any of the @USERn variables in your system, or if there is one available that you are not using, you could do the following. In your routine that launches the window using catalyst, before the window is launched, set @USER1=CATALYST' (or another available @USER variable). Then, in the post-save process from the window, have it check @USER1. If @USER1=CATALYST', then it should immediately return. If @USER1 'CATALYST', then it can continue and do whatever. Then, once the window is closed and control returns to your program, set @USER1='.

You could also use COMMON variables to achieve the same result.

HTH,

msorrel@greyhound.com

Greyhound Lines, Inc.

Instead of