In Update procedure

[Bob Deskin]

Neat! Thanks Peter.

Bob



From:
Peter Bateman <peterbateman808 at hotmail.com>
To:
Bob Deskin/Ottawa/IBM at IBMCA
Cc:
PowerHouse List <powerh-l at lists.sowder.com>
Date:
2009-09-24 01:40 PM
Subject:
RE: In Update procedure




Bob:
 
; to break the entry cycle issue a warning
 
PROCEDURE PREUPDATE
BEGIN 
   PUSH FIND
   WARNING " " ; creates the effect of US
END
 
 
In QKGO SET the command for update return to lower case ur.
In QKGO set  UPSHIFT ACTION commands.
The above takes UR out of the list of actions.
 
PROCEDURE DESIGNER UR
BEGIN
   PUSH UPDATE STAY, RETURN
END
 
In each screen where you want UR you must add the designer procedure.
 
Regards,
Peter Bateman
 
 
 
 
> To: Ken at Langendock.com; wonicon at optusnet.com.au
> Subject: RE: In Update procedure
> From: Bob.Deskin at ca.ibm.com
> Date: Wed, 23 Sep 2009 11:32:44 -0400
> CC: powerh-l-bounces+bob.deskin=ca.ibm.com at lists.sowder.com; 
powerh-l at lists.sowder.com
> 
> There's no direct way to know what the user entered. In most cases it's 
> obvious from the executed procedure.
> 
> For the question Jeff asked, try this:
> 
> screen a
> file file_a
> gen
> subscreen b
> build
> screen b
> file file_b
> gen
> procedure preupdate
> push find
> build
> 
> Get into screen A and do a find. Then call screen B. In screen B, find a 

> record and make a change. Now try your various update commands. You'll 
see 
> (hopefully as in my quick tests) that entering U, US, or UN results in a 

> Find whereas UR gets you back to screen A sitting in the action field.
> 
> If entry is allowed on screen B, it's trickier. Basically, you're 
allowing 
> one entry cycle but after the update you're going into find or leaving 
the 
> screen. I couldn't think of a simple way to do this without modifying 
the 
> ENTRY procedure using a flag to condition processing. Maybe someone else 

> can come up with something.
> 
> Bob
> 
> 
> 
> 
> 
> From:
> "Ken Langendock" <ken.langendock at rogers.com>
> To:
> <powerh-l at lists.sowder.com>
> Date:
> 2009-09-23 09:53 AM
> Subject:
> RE: In Update procedure
> Sent by:
> powerh-l-bounces+bob.deskin=ca.ibm.com at lists.sowder.com
> 
> 
> 
> From what I have found out no, but Bob can confirm.
> 
> This would be a nice new feature for the next release Bob. A new 
> predefined
> variable COMMANDENTERED or something like that?
> 
> Ken
> 
> -----Original Message-----
> From: powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com
> [mailto:powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com] On
> Behalf Of Jeff Hoffman
> Sent: September 23, 2009 9:42 AM
> To: powerh-l at lists.sowder.com
> Subject: [Bulk] In Update procedure
> 
> Hi Guys
> 
> Is there any way of telling in the update procedure if it was 
> triggered by U, US, UN or UR?
> 
> Reason is that for U, US or UN we want to push a find, UR to work as 
> usual.
> 
> Thanks
> 
> Jeff
> 
> 
> 
> -- 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: 'subscribe' in message body to 
> powerh-l-request at lists.sowder.com
> Unsubscribe: 'unsubscribe &lt;password&gt;' in message body to 
> powerh-l-request at lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
> Add 'site:lists.sowder.com powerh-l' to your search terms to search the 
> list archive at Google.
> 
> 
> 
> -- 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: 'subscribe' in message body to 
powerh-l-request at lists.sowder.com
> Unsubscribe: 'unsubscribe &lt;password&gt;' in message body to 
powerh-l-request at lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
> Add 'site:lists.sowder.com powerh-l' to your search terms to search the 
list archive at Google.


Internet Explorer 8 makes surfing easier. Get it now!