Though I have encountered the need a number of times, I have not actually done an application in Access that required a bar code scanner. Here's a not so smart question... How does it work?

That is, I have a potential client who currently uses a web solution with a bar code scanner, but what they are using isn't really doing what they want. They think trying something similar in Access may be the solution.

At present they use a small HP hand held device that allows them to scan certain items. The label on the hand held device says

IPack On Screen data.
and it has an HP Socket Scanner attached to the to it.

So how would something like this work in an Access applicaiton? I mean a person scans a certain item and it gets a number and puts that in some field of a form? Y/N? What does this programmer need to do to create the communication between the scanner the the applicaiton?

What is involved?

What type of barcodes are you talking?

I used to work at a print media company that used "dockets" to track items on an order. Each docket had a unique ID number and it was that number that we used extensively. It was printed on the docket in code 3 of 9 (aka Code39) using a readily available barcode font. In our case, we used Crystal Reports to print the dockets, from a VB6 application, but the font worked in Access reports too.

When someone needed to work on the docket, they would use a wedge-type scanner, which hooks into the keyboard input, to scan the barcode into a specific textbox on the application's form. So effectively reading the barcode emulates the corresponding keystrokes. This approach was very effective as it required no complex programming related to the barcode.

Mike

Thanks Mike for your input.

A wedge-type scanner is an interesting concept. I suppose there are wireless wedge-type scanners. Y/N?

In this case there could be more than on person using a Wedge-type scanner, associated, for example, with PC A. Someone else could be using a Wedge-type scanner that would need to communicate with PC B. Is this a possibility? I.E., two scanners commuincating with two different computers in a wireless configuration?

This was a while ago that I worked at that place, so we had no wireless. These devices were each connected to a PC. However, i would not be surprised if something exists with wireless that offers the same ease of use and implementation, similar to a wireless keyboard.

Mike

Hi Woody

I've developed an application that initially was keyboard input and my client decided that they wanted to use a scanner.

Although at first I was slightly (sic) apprehensive, all it required was the appropriate text box to be selected and the scanner wrote the text string straight into the text box - no changes on my part whatsoever

(There were later changes as a result of using the scanner - but this was only functionality and nothing to do with actually getting the scanned string into the db).

hth

The key here is what the barcode is used for. There can be many answers to that question and without knowing the answer, its hard to advise. I've done three apps that involved scanning a bar code and many that produced barcodes.

One app was a simple POS app. The user scanned each item individually and the barcode was input into a form to pull other info for the item record. On another I used a hand held wand that recorded several codes. The user would scan a code on a box, then scan barcodes on file folders being placed into the box. The wand would then be taken and placed in a cradle. The access app would read the scanned code from the wand ans update the file folder labels to indicate what box they were in. The third was similar, but was an inventory app. Again using a hand held scanner, the user scanned items on a shelf, then scanned the shelf's location code. Again the wand was taken back to a PC, the contents read and an inventory table updated.

I had some similar questions earllier this year. My experience was similar to Pere de Chipstick's.

I hooked up the card reader to the relevant computer through the USB port.

The users opened the Access database, then the correct form. When the form opened, the focus was placed in the relevant text box.

When the card was scanned, the value on the card was placed into the active control on the form. Code in the Change event of the text box then filtered the form to the appropriate record.

It was unbelievably easy.

Now I have been told it will next be a proximity card, one that doesn't need to be swiped, but that can be read once it is within a certain distance of the reader. I have been told by some who know more than I do about this, that it will not be a whole lot different.

Thank you all for your input. This is really good information and make easier for me to understand and determine what to do. I will know more within a week with regard to detail and whether a wedge-type solution will do, or something else.

Thank you again.

Hi, read your interesting Q&A on bar code. Hope you don't mind if I join in, since the experts are at the subject.
These problems I have with Bar Coding have caused some un-productive. [Use in my Inventory Control] measures.
1. How do you send the cursor, automatically to the same field on the next line ready for the next scan, instead of pushing the mouse?
2. How do you print Bar Codes labels of a product Item ID [Alpha/numeric-Code 39] and also define the number of labels required.?
[We print in-house Bar Codes for our Items caused the Vendors' Bar Codes are in-consistent and do not reflex the Item ID in our Access DB]
3. How to print predifined Serial numbers?
Really Appreciate it very much if you could help me on the above.

I've done only one barcode app in Access, but had no problem setting it up using a very inexpensive USB hand scanner. I can answer two of your questions.
1) you can set the focus to any box or control that you want using object.SetFocus, and the behavior of a data grid is to go to the next record when the string is terminated with a return character. In any case that scanner we used was programmable to use nearly any terminate character we needed. The behavior of the data grid itself is programmable in Access Options.
2) The Windows Barcode font is free.
3) You'll need to explain your objective.

Thanks for your reply.
1. Do you have a sample of the procedures on how to send the cursor to same field next line. [My knowledge of Access is limited]
2. How do you activated or make use of the Windows bar Code fonts.? Lets say I wish to print ITEM1234-10-W1-RA-R10
3. I print in-house Serial Numbers like 20120507-001 in bar code labels.
It means the Date of Received [20120507] and shipment one [001] or shipment two [002] and so on.
Lets say I have 10 packages, then I print 10 bar code labels with the same ID and paste them on each package.
I have a table that record other details like Expiry date, Batch No, Lot No and warranty period linked to this Serial ID.
So User just need to scan this Serial No, it will show all the details of the package. [No need to print so many Bar Codes Labels seen on some packages]
The Serial Number is defined in a Table lets say from 100000 to 999999. Everytime I want a Serial Number it will automatically
assign a new next Number, and next ask for "Number of Labels required? Enter the number required and print the Bar code labels.
Merle, this my logic flow, how practical is it, I am not sure. Need experts like you to advise me otherwise I will waste time doing trial and error.
Thanking you and looking forward for your reply.

I think all your reasoning is sound. To print a barcode you just print the characters using the barcode font. No need to overthink this. The only thing you need to investigate is sometimes there is a requirement for a barcode to have an "*" prefix and suffix, and that is a part of programming the hand scanner, but I expect you're doing this in a closed environment where you're making the rules.

Last - you say , and that seems incongruous to me. I learned everything I know doing trial and error; I can't see it as a waste. Some of the questions you have are very detailed, like asking for an example of the text box behavior, and my first thought is - well - find out, see if it works and fix it if it doesn't.

And - I've very pleased to be of some help.

Thanks Merle for your advice. Yes,I will sit back, be a good boy and work out all the "problems" stated. Very true "trial & error" is the key to greatness, but time is not on my side.
Appreciate your help. Keep you posted.