>>
>>How about using your form's Keypress Event to capture those codes and then do your thing?
>
>Thanks, a good idea. I was able to trap the input and prevent the text from going into the textbox. However the keypress event traps only one key at a time and it is difficult to find a key to distuinguish between a scanned entry and a regular keyboard entry. Also, the CHR values have more than one representation (see the INKEY documentation). I think my best bet is to use a string identifier as my scanned 'code' and then to concatenate the string into a property character by character in the form's keypress event. When I have fully identified the scan code I can then take action. I'll try this. Thanks a lot.

AH. Your examples gave me the impression that a single keypress was enough. As far as indentifying the source (scanner vs keyboard), can your scanner be programmed to emit a unique header value you could detect?