You have two ways of information when integrating a bar code system in your app. The first one is reading a bar code to the application. The next one is to generate a bar code from the application.
Depending on your application and your procedures you will need one or both communication ways. Reading the bar code to your app is the easiest part of the job. Just buy and standard bar code scanner and you will see that the drivers normally consider it as a keyboard input. So when you press the button at your barcode scanner is just like writting numbers and some extra keys (like return, tabs, etc.). Some drivers are amazing since they can focus the cursor on a field before inserting the numbers, so you don't need to click on the field before. If not, you can do as I did. I added a big button called "BARCODE SCAN" that only focuses the correct field. The other part is about your report engine. I know that there are solutions to get barcodes at cristal reports, but I'm not aware of them. I didn't need them, since we print tons of barcodes, attach them to the CI's and the scan them to the CMDB. So we always read the barcodes, never print them from the application. Jose Manuel Huerta http://theremedyforit.com/ On Tue, Oct 16, 2012 at 4:33 PM, Grooms, Frederick W < [email protected]> wrote: > > My first suggestion would be to find out which scanner hardware they will > be using. > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
