Screen Processing (AREV Specific)
At 20 JUL 2006 10:15:02AM Daniel Rebich wrote:
Good morning to you all.
Is there a way to have a screen exit on an 'F9' after it saves the record? That is, I'm using CATALYST to call a window with a specific key and after the user enters the information and saves it I want the screen to go away and return control to the program. I've tried post-process on the save and using 'K' {ESC} and that didn't work. any help would be appreciated.
thanks
Daniel
At 20 JUL 2006 12:36PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Setting RESET to 6 on the post save will do it.
World leaders in all things RevSoft
At 20 JUL 2006 03:11PM Daniel Rebich wrote:
I tried that one as well and forgot to mention it; maybe I entered it incorrectly?
WC_RESET%=6
Is there another command that should be included?
Thanks
Daniel
At 20 JUL 2006 03:54PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
We simply created a subroutine, included window common and set WC_Reset% to 6 and it worked. Tested on the 2.1 system we're currently working on but should work on other versions.
World leaders in all things RevSoft
At 20 JUL 2006 11:55PM [email protected] wrote:
works here on 3.12
At 21 JUL 2006 11:38AM Warren Auyong wrote:
It should work so long as you've include WINDOW_COMMON$ or AREV.COMMON
Use WC_RESET% with WINDOW_COMMON$ and RESET with AREV.COMMON
Also one of the other common 'action' variables such as WC_DISPLAY_ACTION$, WC_AMV_ACTION% or WC_WINDOW_ACTION% could affect how the process behaves.
I swear in 1.16 I the order in which I assigned x_action & reset had an effect on the processing. Thus (I don't recall the actual common variables)
x_action=y
reset=x
Return
would not work vs
reset=x
x_action=y
Return
which would.
Big mystery to me because it seems to me that the windows processor would always evaluate these common variables in the order (e.g. x_action then reset) making the order in which they are assigned irrelevant.