Barcodes In Access

[gnasher]

Does anyone have experience in using Access to generate reports with barcodes in them?

I want to be able to encode and print information from my application as a barcode (Probably code 128).

I would also like to rig a scanner up to input information into this application.

Any suggestions for apps / fonts for access 2000 greatfully received.

There seems to be a lot available, I just need something cheap and simple.

Many thanks for your advice in advance.

 

[vbajock]

Eltron and Zebra printers include software that lets you integrate all that kind of stuff in your apps, like barcode fonts etc. They range from 350$ to 5,000$. They also will give you tech support for free in most cases.

If you use a keyboard wedge scanner, you just have to manipulate the setfocus events in your code to position the cursor into the correct field. Once the cursor is in the right place, prompt the user to scan and you will capture the numeric code. Wedge scanners are offered by about a million vendors. Wasp is a good cheapo. If you can't use a wedge scenner and you have to use a Com port, RF or USB interface, hire a programmer and get ready to spend some money.

 

[pgoulet]

Using barcode fonts changes the way that you capture "returning" data forever. Once an understanding of the potential is understood within the organization, everything starts to get a barcode.

Barcodes have to start with an '*' and end with an '*'. So, If you were going to create a control with an account number it would be something similar to:

some control ="*" & [acct#] &"*"
*1234*

Change the font of that control to the barcode font that you want to use. TEST the font, not all fonts are created equally.

There are several BarCode Fonts available. Try one of the free ones or just order one and go through the learning curve. Once you have grasped the basic understanding of the process, the mystery is all gone, but your the guru.

 

[Golom]

If you go with a bar code printer then the whole issue of messing with bar code fonts disappears ... you send ASCII to the printer and it does it's magic. You also get nice side benefits like label-at-a-time printing that you don't get with a page printer.

Most scanners, even the low end ones, are programmable and you can tell them to send only the bar-code characters and strip off all the start-stop stuff so you don't need to deal with it in your application. The big deal with wedge attached scanners is distinguishing between stuff that really was typed on the keyboard and what is scanner input. Being able to make that clear distinction is one reason for the COM or USB attached scanner (and also for the programming cost as vbajock suggests.)

 

[vbajock]

You can't beat the Eltron, or since Zebra bought them Zebra ribbonless thermal printers. They run forever, require hardly any maintenace and they are cheap. The programming kit that comes with them makes programming the stupid things easy, once it's set up you just create a standard Access report, size it to your label and go. This is why UPS uses them by the millions.

 

[JoeCruse]

From what I've seen, the Zebra's software was great, as was the printer...IF you wereonly using one type cardstock on a regular basis. If you have to print on several different types of stock during the day, you have to recalibrate, and it was a pain!

Joe

 

[vbajock]

Yes. It is really designed for high-volumne loading dock apps where you have to print ASN and UPS labels. Not a fancy printer. If you want fancy you need to spring for a Sato or one of the better Zebras.