By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,106 Members | 2,474 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,106 IT Pros & Developers. It's quick & easy.

Barcode scanning interface with access

P: n/a
Hi,

I am in the design phase of building a database that will track the
productivity of my warehouse. I am thinking of using a barcode
scanner to assist me with this. Employees will hopefully be scanning
a barcode which will communicate to the computer that the employee did
some type of task. Employees will be identified by ID badges which
will contain string data to identify them and hopefully log them in.
Is this a good way to keep track of tasks or is another way better?
Keep in mind that we want to change the job as little as possible and
we want to have minimal user interface(I want things to be automated
so people do not have to use the computer). Also, as far as ID's go is
access capable of recognizing individual scanners as identification if
I code it to do so? In addition, is access capable of letting
multiple people use the database at one time to enter their barcodes?
In other words, can I have multiple people doing the same thing at the
same time but with different ID's? Thanks in adavanced for any help
provided!!

Jul 1 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Be sure to use a split database.
Consider using Barcode type 39. It's free and is added to your computer
system as a font.
Look at Zebex.com for a barcode scanner. A scanner is installed in parallel
with your keyboard and acts just like a keyboard. Rather than pressing keys,
you scan a barcode and the "value" fo the barcode is entered into the form.
For printing barcodes in any kind of a report, you use a textbox and set the
font to Barcode Type39. For employee identification, all you need to do is
use EmployeeID. You can print barcodes on a badge by printing labels in
Access. Use a textbox, set the font to Barcode Type39 and print the
EmployeeID.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
re******@pcdatasheet.com



<nm********@gmail.comwrote in message
news:11**********************@q69g2000hsb.googlegr oups.com...
Hi,

I am in the design phase of building a database that will track the
productivity of my warehouse. I am thinking of using a barcode
scanner to assist me with this. Employees will hopefully be scanning
a barcode which will communicate to the computer that the employee did
some type of task. Employees will be identified by ID badges which
will contain string data to identify them and hopefully log them in.
Is this a good way to keep track of tasks or is another way better?
Keep in mind that we want to change the job as little as possible and
we want to have minimal user interface(I want things to be automated
so people do not have to use the computer). Also, as far as ID's go is
access capable of recognizing individual scanners as identification if
I code it to do so? In addition, is access capable of letting
multiple people use the database at one time to enter their barcodes?
In other words, can I have multiple people doing the same thing at the
same time but with different ID's? Thanks in adavanced for any help
provided!!

Jul 1 '07 #2

P: n/a
One way to do this it to keep a hidden form open in the background to
detect when a barcode has been scanned. If you're using keyboard wedge
type scanners, (simplest), you'll need to differentiate between a
barcode and regular keyboard input. You can do this, with code 39, by
intercepting the '*' characters at the start and end of the barcode, and
parsing out the contents. (Don't forget to configure the scanner to
transmit start / stop characters). The logic here is that when a '*'
character is intercepted, the program expects the following characters
up to the next '*' to be a barcode.

Private Sub Form_KeyPress(KeyAscii As Integer)

If bnInBC Then
' we are currently processing a barcode
If KeyAscii = 42 Then
' asterisk entered so stop processing
bnInBC = False
Call ProcessBarcode
strBarcode = ""
Else
' concatenate
strBarcode = strBarcode & Chr$(KeyAscii)
End If
KeyAscii = 0
Else
' start processing barcode if needed
If KeyAscii = 42 Then
KeyAscii = 0
bnInBC = True
End If
End If

End Sub


You'll have to have a timer to exit in case of a bad read of if someone
enters an asterisk from the keyboard. You should be able to find plenty
of code examples to do this. You can also compute a checksum to verify a
good read.

You can develop a prefix library to differentiate the various types of
things that can be scanned, e.g.

'ID' = employee ID
'SI' = stock item and so on

Then you can build up the barcode identifiers using the prefix and an
internal ID, e.g 'ID00123' for an employee. I like to pad numbers with
zeros - it helps when sorting and it just looks nicer when all your
barcodes have the same width.

nm********@gmail.com wrote:
Hi,

I am in the design phase of building a database that will track the
productivity of my warehouse. I am thinking of using a barcode
scanner to assist me with this. Employees will hopefully be scanning
a barcode which will communicate to the computer that the employee did
some type of task. Employees will be identified by ID badges which
will contain string data to identify them and hopefully log them in.
Is this a good way to keep track of tasks or is another way better?
Keep in mind that we want to change the job as little as possible and
we want to have minimal user interface(I want things to be automated
so people do not have to use the computer). Also, as far as ID's go is
access capable of recognizing individual scanners as identification if
I code it to do so? In addition, is access capable of letting
multiple people use the database at one time to enter their barcodes?
In other words, can I have multiple people doing the same thing at the
same time but with different ID's? Thanks in adavanced for any help
provided!!
Jul 2 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.