|
It worked on a 5291 that we have (we only have one terminal so that is all I could try). All terminals may not be the same but it should be simple to try in a sample application. Scott Mildenberger > -----Original Message----- > From: booth@martinvt.com [SMTP:booth@martinvt.com] > Sent: Friday, September 29, 2000 7:07 PM > To: MIDRANGE-L@midrange.com > Subject: RE: keyboard lock on error > > I was happy with ERRSFL too, but does it work for terminals? I haven't > been able to isolate the problem but at one client's shop they have about > 1/2 and 1/2 Client Access and Amber terminals. The terminals require the > error reset but the Client Access doesn't. At least it seems that way. Is > > that possible? > > _______________________ > Booth Martin > Booth@MartinVT.com > http://www.MartinVT.com > _______________________ > > > > > Scott Mildenberger <Smildenber@Washcorp.com> > Sent by: owner-midrange-l@midrange.com > 09/29/2000 04:25 PM > Please respond to MIDRANGE-L > > > To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com> > cc: > Subject: RE: keyboard lock on error > > Lance > > Try using the ERRSFL keyword in your display file, I was so happy when I > discovered it. > > Scott Mildenberger > > > -----Original Message----- > > From: Gwecnal@aol.com [SMTP:Gwecnal@aol.com] > > Sent: Friday, September 29, 2000 10: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 > > +--- > +--- > | 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 > +--- > > > > > +--- > | 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 > +--- +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.