|
Actually, I don't really see your problem. Tell your users to hit the [Tab] key and not the [Arrow] keys. [Tab] is a standard for windows, people just don't realize it. Sometimes it is poor Windows programming that makes it unusable, most of the time it is just the users that don't know to use it. Regards, Jim Langston Rajeev_Asthana@paramount.com wrote: > Booth, > > No. I meant that instead of using Tab key , users use arrow keys and then >type > at non-input capable area somehow, say for example, by mistake hit space bar >and > then they lock their keyboard. > > Rajeev. > > boothm@ibm.net on 09/07/99 09:15:06 PM > > Please respond to MIDRANGE-L@midrange.com > > Subject: Re: Keyboard Lock > > Rajeev, I misunderstood the problem you describe. I also can't duplicate > the problem. You say the user uses an arrow key and gets off the input > capable field and then types a letter and the keyboard locks up? I can > understand it not accepting the key stroke, but what does "keyboard lock" > mean? I just tried it and the keyboard didn't lock. I tried it both with > Client Access Express and with OS/2 Communications. > > In <882567E6.0002C1A7.00@gump.paramount.com>, on 09/07/99 > at 05:27 PM, Rajeev_Asthana@paramount.com said: > > >Hi Dan, > > >My users are using Extra Attachmate on Win95. > >They have been told to use Tab keys but there are some clever users who > >try arrow keys and land in problems. > > >Rajeev. > > >"Dan Bale" <dbale@genfast.com> on 09/07/99 10:04:55 AM > > >Please respond to MIDRANGE-L@midrange.com > > >Subject: Re: Keyboard Lock > > >Rajeev, > > >>Is there any way to ignore typing on non-input capable area so as not to get > >>keyboard lock? > >>My users are 'goddaming' about red 0005 error and key board locking. > > >Previous respondents have mentioned ERRSFL, but I fail to see how that > >will help in your case. > > -- > ----------------------------------------------------------- > boothm@ibm.net > Booth Martin > ----------------------------------------------------------- > > +--- > | 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.