Push Command

[Tony Knowles]

We used to use a scheme whereby the entry procedure processing was moved to
an internal procedure called from a dummy entry procedure. The internal
procedure was run recursively until a data OK = yes prompt was entered by
the user. Data input in clusters was terminated by pressing <return>. We did
this in an attempt to make the screens easier to use, the users didn't need
to remember or know about '//' etc. However when some smart users came along
and entered '//' to signal end of input, QUICK would freeze up, never did
track down why. We have since removed all this code and now screens function
normally (at least as far as QUICK is concerned).
Tony Knowles

> -----Original Message-----
> From: owner-powerh-l@sphere.swau.edu
> [mailto:owner-powerh-l@sphere.swau.edu]On Behalf Of Walker, Chris
> Sent: Thursday, 10 June 1999 14:45
> To: powerh-l@lists.swau.edu
> Subject: RE: Push Command
>
>
> I've accomplished something similar as follows:
>
> CLUSTER OCCURS 10
>   FIELD ACCOUNT-NUMBER ENTRY IF OCCURRENCE EQ 1 OR PROMPTOK
>   FIELD ACCOUNT-AMT ENTRY IF OCCURRENCE EQ 1 OR PROMPTOK
> CLUSTER
>
> This stops prompting as soon as the user just presses <Return> in a field,
> but there's no reason why you couldn't substitute another
> condition, such as
> T-AMT-LEFT EQ 0.
>
> Chris Walker
> Tate & Lyle
> London

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.