|
midrange.com
I'm not sure why I thought of this since it's been a couple of days, but I
did. When I used to work with Telxon/Symbol scanners I ran into the same
problem of user's not stopping their scanning to read error messages. The
solution I used in that case was to throw up a screen that displayed the
error message but had no input-capable fields. Because there was no place
to type, the scanner wouldn't scan, and they would stop to read the screen.
Even though the scanners were DOS-based the integration between the 5250
client software and the hardware was pretty good. I've looked at other
Windows-CE scanners but they didn't have that integration. This technique
did NOT work with scanners plugged into a PC keyboard jack.
I haven't worked nearly as much with barcode scanners for the past few
years so things may have changed.
Dave Parnin
--
Nishikawa Standard Company
Topeka, IN 46571
daparnin@xxxxxxxxxxxxxx
"Hauser, Birgitta"
<Birgitta.Hauser@LP- To: "'Midrange Systems
Technical Discussion'"
GMBH.com> <midrange-l@xxxxxxxxxxxx>
Sent by: cc:
midrange-l-bounces@m Subject: AW: Can't lock
keyboard on errors
idrange.com
04/19/2006 02:47 AM
Please respond to
Midrange Systems
Technical Discussion
Hi,
I did not try it but:
Define a message row and add an indicator to activate the message row in
your DDS.
Move the error message into this message row and move on the indicator to
show the message.
Using a message row will lock the keyboard as soon as the indicator gets
turned on.
Birgitta
"If you think education is expensive, try ignorance"
(Derek Bok)
-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Dave Murvin
Gesendet: Dienstag, 18. April 2006 22:44
An: midrange-l@xxxxxxxxxxxx
Betreff: Can't lock keyboard on errors
Hi,
We have a warehouse application where users are scanning info through
bar code wedge readers into a 5250 application displayed with Client
Access. Since they are not always looking at the display when they are
scanning information, they want the error messages to lock the keyboard
to prevent any other entry until they press the reset key.
I have tried the LOCK keyword, along with the ALARM keyword on all
record formats and on the SFLCTL record on our message subfile (which we
display on line 24). The ALARM works, but I can not get the LOCK
keyword to lock the keyboard (it uses the same indicator as the ALARM
keyword).
I looked though the archives, but everything seemed to be related to not
locking the keyboard.
Any suggestions?
Thanks
Dave
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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.
