Update Stay

[Pickering, John (NORBORD)]

I'm happy to learn from Bob that there really isn't any way to detect
which Update command the user entered. I've looked and never found one.

What I have done in a couple of cases is to make the Update Stay command
behave like the others by pushing Enter or Find (depending on mode) in
the Postupdate procedure. Then I know the buffers aren't hanging around.
This was useful when the update changed something that would affect the
retrieval that Quick was doing.

JWP

-----Original Message-----
From: powerh-l-bounces+john.pickering=norbord.com at lists.sowder.com
[mailto:powerh-l-bounces+john.pickering=norbord.com at lists.sowder.com] On
Behalf Of Bob Deskin
Sent: Thursday, June 04, 2009 2:52 PM
To: Karen Barrett
Cc: powerh-l-bounces+bob.deskin=ca.ibm.com at lists.sowder.com;
PowerhouseList Post
Subject: Re: Update Stay

Unless someone's found a back door or a hack, there's no way to
intercept 
a QUICK command. However, there is a sneaky way to possibly do what you 
want. The downside is that it will affect every screen.

Normally, QUICK commands are case insensitive. Plus, they are checked 
first when you enter something in the action field. So even if you
create 
a DESIGNER procedure named US, the QUICK command US comes first.

The way around this is to use QKGO. First make sure that Upshift Actions

is set to Y in the Execution-Time Parameters screen. Next go to the
Action 
Field Commands screen and change the Update Stay command to lower case
us. 
It can actually be any lower case characters but I like to use us so
that 
it reminds me of what I'm trying to hide.

At this point, if the user entered us or US, they would get an Unknown 
Command message because whatever they enter is upshifted but the command

is in lower case.

Now write a DESIGNER procedure named US. You can either code your
special 
US logic in the designer procedure or set a flag that you can test in
the 
PREUPDATE. Also, code a PUSH UPDATE STAY so that you get the same
command 
execution as the user entered.

The downside is that this will affect every screen using this QKGO file.

So you'll have to code a US designer procedure with PUSH UPDATE STAY.

Bob



From:
Karen Barrett <kbarrett00 at hotmail.com>
To:
PowerhouseList Post <powerh-l at lists.sowder.com>
Date:
06/04/2009 02:32 PM
Subject:
Update Stay



Hi All,
 
I don't see it anywhere in the documentation but what I would like to do

is put some conditional processing in the preupdate module if the user
has 
entered US but not U or UN or UR.
 
Has anyone found a little trick for this? US keeps the record buffers
but 
that does not help me until postupdate right?
 
Thanks,
 
Karen Barrett
Elk Point, SD