No Subject

[owner-midrange-l@xxxxxxxxxxxx]

<E4C0F071C1ADD211BFB00008C7B20EE007279C6F@endeavor.bentlynevada.com>
From: "MCPARTLAND, Stan" <stanley.mcpartland@bently.com>
To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
Subject: RE: keyboard lock on error
Date: Fri, 29 Sep 2000 14:56:16 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
        charset="iso-8859-1"
Sender: owner-midrange-l@midrange.com
Reply-To: MIDRANGE-L@midrange.com
Errors-To: list-errors@midrange.com
X-List-Name: Midrange Systems Mailing List (MIDRANGE-L@midrange.com)

Lance,
Try the file level keyword ERRSFL.  This causes error messages generated
from ERRMSG, ERRMSGID, SFLMSG, SFLMSGID, VALUES, RANGE, etc. to be placed in
a subfile on the message line and the keyboard is not locked.

If you want more flexibility in your message processing, you can add a
program message subfile to each display and use the message APIs to send
your error and other messages.

Regards,
Stan

-----Original Message-----
From: Gwecnal@aol.com [mailto:Gwecnal@aol.com]
Sent: Friday, September 29, 2000 9:48 AM
To: MIDRANGE-L@midrange.com
Subject: keyboard lock on error


Does anyone know a way to disable the 'keyboard lock on error' function?
My users find it frustrating to have to press the 'Mommy may I?' key before
being
allowed to correct their errors, and I agree.  I don't use the error message

keyword
for this reason, I don't use the VALUES or RANGE function either.  When you
make a mistake, the system already positions the cursor, displays a message,
and highlights the field.  It should just let you key the correction.
Thanks, Lance 

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---