|
Thanks Dave. They have another application here that does what you suggested, but I was hoping to get it to work with the DDS code. I ended up doing something similar to your solution. I created s simple window without any input fields that displays the error message. They must manually press a function key on the window to return to the application. Text for the window error message and the command key text are input parms and the response is an ouput parm from the window, so program can be used anywhere. Thanks Dave Dave wrote: 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
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.