General Barcode and Access
Hi,
I have done some research on the web regarding Barcoding and MS Access.
One thing I can't seem to get my head around, or find an answer for is this;
How does the data from the scanner get into the database?
If using a wireless scanner in a warehouse and I want to send data to the database, do I need to have a form open on the workstation that would accept the data scanned?
Similarly, if people are scanning products on the shop floor, would that not need a different form open?
I currently handle all stock movements and stock levels by action queries and vba behind input forms. But my boss is willing to pay for scanners if I can just get my head around the sequence of events needed.
As always any advice, or pointers to relevant articles is welcome.
Thanks
I have done some research on the web regarding Barcoding and MS Access.
One thing I can't seem to get my head around, or find an answer for is this;
How does the data from the scanner get into the database?
If using a wireless scanner in a warehouse and I want to send data to the database, do I need to have a form open on the workstation that would accept the data scanned?
Similarly, if people are scanning products on the shop floor, would that not need a different form open?
I currently handle all stock movements and stock levels by action queries and vba behind input forms. But my boss is willing to pay for scanners if I can just get my head around the sequence of events needed.
As always any advice, or pointers to relevant articles is welcome.
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I also presume a separate table would be needed to capture the scanned data which would clear when the data has been "pushed" to the respective tables relevant to what was scanned.That's generally a good idea. It allows you to validate your data before it hits the live table, at the expense of potentially "stale" data, depending on how often you process the staging table.
ASKER
Thanks again to all for the input
ASKER
We have dedicated Wi-Fi throughout the site and my intention was to get wireless scanners so that trained personnel could scan at their respective locations and then 'send' the data back to the database. I have found some "Wedge" type software from TEC-IT, namely the TWedge, which seems to fit the bill, so I guess it's down to the scanner and probably batch-type. I also presume a separate table would be needed to capture the scanned data which would clear when the data has been "pushed" to the respective tables relevant to what was scanned.