It is easy to use a portable data collector to scan UPC barcodes, RMS barcodes, etc. My problem begins when the delimited text file is being imported.
About 1% or 2% of the time, my scanning people scan the wrong label. They get the manufacturer's internal barcode, or whatever might be on the packaging. If one looks at the text file, it looks normal. You only know that you have a problem while in the middle of the import process. If the barcode doesn't match an ILC or an Alias, it is flagged as an "Entry with errors". Now, I have no idea what they were scanning.
In my previous POS system, one could at least see what came immediately before, and immediately after the 'bad' data.
0099999 Glove XL 0099997 Glove L 009120 "entry with errors" 0099996 Glove S Once I saw this data, I could tell them "Go re-scan whatever came between the large & small gloves".I wish I could print the data that is on the screen at that point in the import process. I can't print it or copy it to the clipboard. I can only take screenshots.
Surely someone else has this problem. Any workarounds?
It would help to know which tables hold the data in the StoreOps database. I could at least get at it with a report.
Tim Gale Bicycle Garage Indy, Inc.