Forgive me if this has been asked elsewhere, I couldn't find any similar posts when I looked.
I have a DB that I use to print to a thermal printer to make barcode labels. These barcodes are each a unique number and are usually printed in a sequence of 500 at a time. It creates one report with each page being one label. The problem I am finding is that on occasion, the print spooler seems to resend the entire the job to the printer causing whatever numbers were already printed to be duplicated. From what I can tell in other searches is that it's likely happening if the printer, spooler or network drops the job, it can be resent again causing it to start over. So the next solution I'm looking at is having to revise the process so that it creates a 1 page report for each number in the sequence - thereby creating 500 print jobs being sent to the printer instead of just one.
Can anyone advise if there is a better solution than dumping that many jobs to the printer, or is that likely the best solution as any lost job should be resent? Could a job get locked or skipped and cause the sequence to be printed out of order? I don't imagine it's easy if even possible to detect when the job gets dropped or restarted?
Thank you in advance.