Duplicated prints when printing different records too close to each other S’abonner



I have a customer that have a production system with bartender 2016 automation integrated (.NET SDK). It is setup with the textfile (csv) database option in bartender because of the need to order multiple labels together when printing without a cut between all labels. Named data sources are not working like this and therefore we use the database option.

One problem that has occurred is that sometimes they print the same btw document from different computers at approximately the same time, or prints the same document to close to each other from the same computer. When this happens records from one print is skipped and instead bartender prints duplicated prints of the other print. I think the problem is the csv file is updated to quickly before bartender had the time to print the record and then prints the record for the next print instead.

I tried to create csv files dynamically from the code instead of using the same file. But this didn't work, it crashed on this row because the textfile isn't setup as a database.


Is there a way to do something similar like what I tried from the .NET SDK?

2 commentaires

Xabier Clemente
Actions pour les commentaires Permalien

Hi Victor,

Welcome to the BarTender Community!

In order to properly troubleshoot this issue, we would appreciate it if you could answer a few questions:

  • Could you tell us what BarTender 2016 Service Release are you currently on?
  • Also, the .NET SDK is just one form of printing; to verify that no crashing/duplicates/skipping is happening, could you test if the issue is still present just using BarTender Designer? Do you still experience this issue?


Victor Gregebo
Actions pour les commentaires Permalien

Hi Xabier,

Thank you!

We use BarTender Designer 2016 R9.

I think this is hard to test from Bartender Designer because I have to be very quick to update my textfile database between the prints. Im thinking about solving this by adding maybe two more textfile databases (total of three) and from the application specify which one to use. Because the problem is that two different prints use the same file at the same time (with different data) and this causes duplicates.

What do you think about that solution?



Vous devez vous connecter pour laisser un commentaire.