Hi There,
we use bartender commander v7.00 build 895 on win2k svr to pick up barcode (*.dd) files from a trigger directory and feed the contents and preformatted lable (*.btw file) into a bartender.exe service to print labels.
We have found that this process fail regularly. I beleive due to 2 instances to bartend.exe running at the same time (commander effectively does know to which process to hand information to). Labels then queue up as the process fails to consume *.dd files
Has anybody had similar expierences with bartender commander? Any tips or thoughts are welcome.
The issue with 2 instances of bartend.exe also happens when bartend.exe is called via the API, again stopping printing. This was the origional reason why Seagull persuaded use to move to commander.
We print about 4000 labels a day
Thanks,
Joe
we use bartender commander v7.00 build 895 on win2k svr to pick up barcode (*.dd) files from a trigger directory and feed the contents and preformatted lable (*.btw file) into a bartender.exe service to print labels.
We have found that this process fail regularly. I beleive due to 2 instances to bartend.exe running at the same time (commander effectively does know to which process to hand information to). Labels then queue up as the process fails to consume *.dd files
Has anybody had similar expierences with bartender commander? Any tips or thoughts are welcome.
The issue with 2 instances of bartend.exe also happens when bartend.exe is called via the API, again stopping printing. This was the origional reason why Seagull persuaded use to move to commander.
We print about 4000 labels a day
Thanks,
Joe