Suppress keyboard, allow barcode scanner

I posted yesterday about a project I'm involved in to build a login
application using a barcode scanner.

I've solved most of the problems, but one remains. The client want to
disable keyboard input (except at some remote sites where there won't
be a scanner). The session "knows" whether that site should be
keyboard enabled, but unfortunately the output from the scanner is in
the form of keypresses! So any attempt to capture and suppress
physical keypresses in script cannot differentiate between keyboard and
scanner.

Anyone got any ideas?

EdwardNope... you are probably out of luck, especially since it's a Web interface.
You would have to have some sort of client addin/component built and
installed but in the end even that may not help since the scanner simply
emulates a keyboard.

--
Curt Christianson
site: http://www.darkfalz.com
blog: http://blog.darkfalz.com

"teddysnips@.hotmail.com" wrote:

> I posted yesterday about a project I'm involved in to build a login
> application using a barcode scanner.
> I've solved most of the problems, but one remains. The client want to
> disable keyboard input (except at some remote sites where there won't
> be a scanner). The session "knows" whether that site should be
> keyboard enabled, but unfortunately the output from the scanner is in
> the form of keypresses! So any attempt to capture and suppress
> physical keypresses in script cannot differentiate between keyboard and
> scanner.
> Anyone got any ideas?
> Edward
>
teddysnips@.hotmail.com wrote in news:1129216453.891262.133020
@.g47g2000cwa.googlegroups.com:

> I posted yesterday about a project I'm involved in to build a login
> application using a barcode scanner.
> I've solved most of the problems, but one remains. The client want to
> disable keyboard input (except at some remote sites where there won't
> be a scanner). The session "knows" whether that site should be
> keyboard enabled, but unfortunately the output from the scanner is in
> the form of keypresses! So any attempt to capture and suppress
> physical keypresses in script cannot differentiate between keyboard and
> scanner.
> Anyone got any ideas?

With IE, you cannot disable ALL keystrokes anyways.

If there is a such a requirement, you might want to consider using a
winforms login page instead... and somehow tie it into your web app.

--
Lucas Tam (REMOVEnntp@.rogers.com)
Please delete "REMOVE" from the e-mail address when replying.

Newmarket Volvo Sucks! http://newmarketvolvo.tripod.com
you would need an write active/x control. you would then plug the scanner
into a seperate serial port (not the keyboard). the active/x control would
then poll the scanner's serial port for input, and raise an event on input
for client script to handle. you would use a hidden field that the client
script used to post the login id, so the keyboard would be disabled.

-- bruce (sqlwork.com)

<teddysnips@.hotmail.com> wrote in message
news:1129216453.891262.133020@.g47g2000cwa.googlegr oups.com...
>I posted yesterday about a project I'm involved in to build a login
> application using a barcode scanner.
> I've solved most of the problems, but one remains. The client want to
> disable keyboard input (except at some remote sites where there won't
> be a scanner). The session "knows" whether that site should be
> keyboard enabled, but unfortunately the output from the scanner is in
> the form of keypresses! So any attempt to capture and suppress
> physical keypresses in script cannot differentiate between keyboard and
> scanner.
> Anyone got any ideas?
> Edward
Bruce Barker wrote:
> you would need an write active/x control. you would then plug the scanner
> into a seperate serial port (not the keyboard). the active/x control would
> then poll the scanner's serial port for input, and raise an event on input
> for client script to handle. you would use a hidden field that the client
> script used to post the login id, so the keyboard would be disabled.
> -- bruce (sqlwork.com)

Thanks to you and to all other respondents. It's a fixed price
contract and we've agreed the work, so I'll just tell them to remove
the keyboard. That's the easiest solution, and the most foolproof
(until the scanner goes AWOL).

Edward