Hi Mark,

Thanks for the responses. The timing method looks most promising. The position of the cursor is already obvious but the cashiers sometimes move product and happen to pass thru the scanner by accident. I think I will also require the user to press tha enter key. That way I can check the time between the last keystroke and the CRLF.

Another idea I had involved identifying the numeric keypad. There is a way to do that but I'm not sure whether the scanner emulates the numeric keypad or the regular numbers.

Thanks for the ideas. Too bad there is not a way to programatically turn the scanner on and off.

Ken

>One way is to time how fast the characters are coming into your keypress event. A human can't type nearly as fast as a scanner. If characters are coming in faster than a human can type, clear the field.
>
>Another way is to make it very obvious where cursor is at with a big colored box around current input field. That little blinking cursor or selected back color is hard to find but a big white/yellow/red/black box makes it easier to see where current input is.
>
>Still another is to add a maximum customer change amount setting. Most could run it at $100. A warning message would appear if change was more than $100 and request a manual approval. Clear the typeahead buffer before displaying the message.
>
>>Hi,
>>
>>In our POS Application, users will sometimes inadvertently scan a barcode when the app is expecting an amount tendered (a numeric field). Since the scanner is set to add a CRLF the app thinks the amount tendered is some huge amount and happliy tells the cashier to give the customer a nice fat amount of change.
>>
>>Is there anyway to tell the app to accept data from the barcode scanner only when I want a barcode?
>>
>>Thanks,
>>
>>Ken