Printing Problem Error Message #3300
We have designed a label layout using Bartender software and created a program to store all required data into a text file and download into the C drive. The program will then trigger the printer to print the label with the layout and data text file.
The label layout is also stored in C drive.
When the program is run, the data text file is created in the designated folder. However, once we click print or preview, this error will appear,
"BarTender: Error Message #3300.
Cannot find the above file. Please verify that the correct path and file name are given."
We checked the folder and found that the data text file is deleted.
Can you help us?
Thank you.
-
How is BarTender being triggered to pick up the data file to produce a print job from it? Please explain the mechanism. What you describe is the exact function that of what Commander does. See the below white papers:
http://www.bartenderbarcodesoftware.com/label-software/whitepapers/Commander-Examples(English).pdf
0 -
I am having the same issue. I use commander with file triggers. What is happening is that the text file is is created from printing. Label.txt then commander sees it and renames it label.old. It then sends it to the pritner. The first label prints, but the next one throws out the error refering to the .old file that just printed. Once I click ok, it then prints the next label and so on.
I have the task to print immediate and I have also tried to have it poll for 1 second getting the same results. Why would commander be looking for a file after the label has been printed?
Below is what I have in the .lbl file.
[DELIMITERS] {}
[FILE] \\sql1\commanderwatch\Label-{SHIPMENT(TRIM=LEFT)}-{TARENUM(TRIM=LEFT)}.DAT
[LABEL]
%BTW% /AF="C:\program files\bartender\labels\Label.btw" /D="<Trigger File Name>" /PRN="Zebra ZM400-1" /R=3 /P /DD
%END%
"{SHIPMENT}","{VNUM}","{ORDNUM}","{ORDNUMLIST}","{DEPT}","{CARRIER}"
[END]
THIS IS THE COMMENT AREA..0 -
PCavanaugh: Attach the actual trigger file, Commander task list file, and the BarTender document file for me to examine. To fault find Commander issues, please follow the instructions found in the Commander trouble-shooter document: http://forums.seagullscientific.com/index.php?/topic/55-commander-troubleshooting
0
請登入寫評論。
評論
3 條評論