Re: Prompting in a Program

[Alan <cfuture@xxxxxxxxxxx>]

Yep, that's how I'm handling it in my programming, except for the 
numeric row and cursor re-positioning. I felt safe enough, including the 
case where another programmer moves them around on the screen, because 
the cursor positioning on the output is exactly the same as on input, no 
matter where the field moves to.

On the other hand, I may revisit even that after this conversation, as 
for most of these fields I do set up the DSPATR(PC) keyword set up, for 
the error validation routines. There's no way around using indicators 
for that in the DSPF, oh well.. But I do rename them inside the RPG, and 
give them each a SETOF(nn 'text description explaining the indicator..') 
pair.

--Alan
.
> We do the same thing, except we check for the field name. When F4 is pressed, I do a 
> Select group for each cursor field that can be prompted. The OTHER clause sends an error 
> message, "Prompt not available for this field.". I don't like to use row and 
> column because someone will change the screen around without changing he row and column 
> in the program, and all of a sudden, the prompt doesn't work anymore. Plus I don't have 
> to convert the position from binary.
>
>
> Francis Lapeyre
> IS Dept. Programmer/Analyst
> Stewart Enterprises, Inc.
> E-mail: flapeyre@xxxxxxxx 
>
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Alan
> Sent: Sunday, July 02, 2006 2:31 PM
> To: RPG programming on the AS400 / iSeries
> Subject: Re: Prompting in a Program
>
> I also use the cursor row and column to return the cursor to the field
> prompted. Optionally you could send it to the next field, for which you
> would have to do a bunch of extra setup.
>
> --Alan