--------------048FEE6DB3FA8753EA2BBF4A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The code didn't quite come out on the original message for some reason. It is as follows: screen callingscreen etc. file WHATEVER designer etc. procedure designer 99 begin run screen calledscreen passing... let item of WHATEVER = systime put WHATEVER reset end If you use the method where you try to override what the user uses to exit a screen you must keep in mind the '^', the '^^' and the '^^^'. These all would have to be overridden in the QKGO file. While this could be done if it's an existing system retraining would be required. To override these values just change them to a lowercase character value such as 'x', 'xx' & 'xxx' and then set the upshift actions parameter to 'Y'. Regards (again) Michael Lee MCL Systems Inc. Michael C. Lee wrote: > You might want to consider a slightly different tactic. Instead of doing all > that work to do PUTs when you leave a screen perhaps you should go up a level > and do the PUTs when you come back from the screen in question. This might be a > bit of work if the screen(s) in question are called from a lot of other screens > though. We did something similiar on a system I worked on with code along this > lines.... > > screen callingscreen --------------048FEE6DB3FA8753EA2BBF4A Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit The code didn't quite come out on the original message for some reason. It is as follows:screen callingscreen
etc.
file WHATEVER designer
etc.
procedure designer 99
begin
run screen calledscreen passing...
let item of WHATEVER = systime
put WHATEVER reset
endIf you use the method where you try to override what the user uses to exit a screen you must keep in mind the '^', the '^^' and the '^^^'. These all would have to be overridden in the QKGO file. While this could be done if it's an existing system retraining would be required. To override these values just change them to a lowercase character value such as 'x', 'xx' & 'xxx' and then set the upshift actions parameter to 'Y'.
Regards (again)
Michael Lee
MCL Systems Inc.
Michael C. Lee wrote:
You might want to consider a slightly different tactic. Instead of doing all
that work to do PUTs when you leave a screen perhaps you should go up a level
and do the PUTs when you come back from the screen in question. This might be a
bit of work if the screen(s) in question are called from a lot of other screens
though. We did something similiar on a system I worked on with code along this
lines....screen callingscreen