Jeff, The typical hand held bar code scanner with a trigger that I am familiar with in a point of sale system (Quickbooks POS) simply sends just a text code (numeric or Alpha or both) of the bar code scanned to whatever is receiving it. One can see this when setting up a new system and testing the bar code scanner. Bar codes typically have a beginning and ending code so it knows where to begin reading the code and when it is at the end. I presume this is internal to the scanner.
I pulled the following off the internet, and the point to this is essentially, the bar code scanner duplicates a keyboard entry. In point of sale system, the UPC field for item entry generally can be either scanned or keyed in. So not sure how one could make the distinction between scanned and manual key, but maybe separate columns for each, the default column accepting only scanned codes, the second, a keyed entry. Barcode scanners can be classified into three categories based on their connection to the computer. The older type is the RS-232 barcode scanner. This type requires special programming for transferring the input data to the application program. "Keyboard interface scanners" connect to a computer using a PS/2 or AT keyboard–compatible adaptor cable (a "keyboard wedge"). The barcode's data is sent to the computer as if it had been typed on the keyboard. Like the keyboard interface scanner, USB scanners are easy to install and do not need custom code for transferring input data to the application program. On PCs running Windows the HID interface emulates the data merging action of a hardware "keyboard wedge", and the scanner automatically behaves like an additional keyboard. Steve J Original message From: "Richardson, Jeff" <[email protected]> To: [email protected]; Dated: 3/8/2017 9:57:59 AM Subject: Re: [RBASE-L] - Typed versus Scanned Thank you all for your responses and suggestions. For any one curious, I am trying to integrate a simple Willingo "Ring" 1D portable barcode scanner model 2601 into my data collection form. No form button is required to initiate the scanner. Pressing the trigger on the scanner sends the scanned data to any focused field. A "carriage return" of sorts seems to follow the scanned value because the focus jumps to the net field after scanning. Karen: I looked up the "counting characters" code you mentioned being previously posted in rbase-L and found it promising to my situation. I will attempt to develop this for my needs. Dan: I like the idea of a special character. If the counting characters method fails to prove useful, I might contact the manufacturer about how to do this, but I hate the thought of programming each scanner and ensuring that every form field strips it out before processing. Thanks again! From: karentellef via RBASE-L <[email protected]> Sent: Wednesday, March 8, 2017 8:28 AM To: [email protected] Subject: Re: [RBASE-L] - Typed versus Scanned I'm guessing he's using one of those "keyboard wedge" (?) kind of scanners, no button is needed to launch. The cursor is in a field, you run a scanner and it puts it right in the field, so nothing needs to be initiated. I don't use the keyboard scanners, just batch-type of scanners. In that case, as you are suggesting, the scanner also brings in a date/time field which I store in another column so I am able to tell whether data came in via scanner or not Karen -----Original Message----- From: Bruce Chitiea <[email protected]> To: rbase-l <[email protected]> Sent: Tue, Mar 7, 2017 4:56 pm Subject: Re: [RBASE-L] - Typed versus Scanned FWIW: Speaking out of near total ignorance here, it strikes me that this information might be captured at data-input time. Presumably there's a button pushed to initiate a routine which launches the scan and capture. Might not a column be added <wherever> to capture the fact that a scan was performed for this/these particular piece/s of data? Might this value find its way into a form variable text control displaying the scanned/typed status of the adjacent data value? Bruce Chitiea SafeSectors, Inc. 909.238.9012 Mobile ------ Original Message ------ Sent: 3/7/2017 5:28:04 AM Subject: [RBASE-L] - Typed versus Scanned From: "Richardson, Jeff" <[email protected]> To: "[email protected]" <[email protected]> Cc: I want to be able to tell if a value has been scanned (using a bar code scanner) or typed (using the keyboard) into a form's variable memo field upon exiting the said field. Does anyone have a method to make this determination that they'd generously like to share with me? Thanks in advance. Jeff Richardson Charleston, WV ATTENTION: This message and all attachments are PRIVATE, and may contain information that is CONFIDENTIAL and PRIVILEGED. If you have received this message in error, please notify the sender by reply e-mail and delete the message immediately. To unsubscribe from marketing and sales emails, please reply unsubscribe in the subject line. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
