Hi all,
I did a few barcode projects a few years back and I'm sure things have changed. My question is: What would a standard (or common) method be of getting input to a vb program from a swiping device, either a keyboard or standalone cardswipe? This would be for timeclock input, so people would be just walking up and swiping one-by-one. I'm not really concerned about the 'final destination' as far as the database at this point, just the raw collection of the data.
For example--and as a point of reference to what I'm used to--in the past I'd have a vb exe running with the msComm control, and the barcodes came in via serial port and I used the control's event (I've even forgotten the eventname, I think it was OnComm) to process the input. Although this worked very well, it seemed kludgey then and I've got to think it's even kludgeier now. Would this still be an acceptable or 'standard' way (if there is any such thing) of collecting input? I'm not even sure if the interface will be serial or usb or ethernet or whatever.
I'd like to avoid having to have a vb exe running--maybe a dll running as a service instead (this will be on Win 2000 server), or whatever. I guess I'm just looking for a very general outline of what would be a good starting point, since I just remember the msComm control being tedious to work with. Thanks for any advice,
--Jim
I did a few barcode projects a few years back and I'm sure things have changed. My question is: What would a standard (or common) method be of getting input to a vb program from a swiping device, either a keyboard or standalone cardswipe? This would be for timeclock input, so people would be just walking up and swiping one-by-one. I'm not really concerned about the 'final destination' as far as the database at this point, just the raw collection of the data.
For example--and as a point of reference to what I'm used to--in the past I'd have a vb exe running with the msComm control, and the barcodes came in via serial port and I used the control's event (I've even forgotten the eventname, I think it was OnComm) to process the input. Although this worked very well, it seemed kludgey then and I've got to think it's even kludgeier now. Would this still be an acceptable or 'standard' way (if there is any such thing) of collecting input? I'm not even sure if the interface will be serial or usb or ethernet or whatever.
I'd like to avoid having to have a vb exe running--maybe a dll running as a service instead (this will be on Win 2000 server), or whatever. I guess I'm just looking for a very general outline of what would be a good starting point, since I just remember the msComm control being tedious to work with. Thanks for any advice,
--Jim