Re: Indicator Coding Technique

["Denis Robitaille" <denis_robitaille@xxxxxxxxxxxx>]

But, if memory serves me right, when we use this keyword, we must press "reset" 
to regain access to the keyboard. Also, this forces me to use an indicator for 
each error condition. But you are right, it would take care of the cursor 
positioning and highlithing. In our case, we would use ERRMSGID instead of 
ERRMSG since our system support several languages.

Thanks for the info.

Denis Robitaille
Directeur services technique TI
819 363 6130

SUPPORT
Jour (EST) Daytime : 819-363-6134
En-dehors des heures (EST) After hour : 819-363-6158
Network Status : 819-363-6157

>>> booth@xxxxxxxxxxxx 2006-01-12 16:10:16 >>>
Consider using the EERRMSG keyword for errors.  There's no need for you 
to position the cursor.

"When the message is displayed, the following conditions occur:

For all errors:
The message is highlighted.
... (snip)...
The cursor is repositioned to the first displayed field that is in error.

...'



Denis Robitaille wrote:
> I like most of this post.
> ...
> I also want to stress that using the display file data structure to find out 
> the pressed key is the way to go. this way, all keys can be treated the same 
> way (function keys, page up/down, print screen, even enter).
> 
> Denis Robitaille
> Directeur services technique TI
> 819 363 6130
> 
> SUPPORT
> Jour (EST) Daytime : 819-363-6134
> En-dehors des heures (EST) After hour : 819-363-6158
> Network Status : 819-363-6157
> 
> 
-----------------------------------
Booth Martin
http://martinvt.com 
-----------------------------------