Strange Problem With Text File Data Source 关注

0
Avatar
Legacy Poster

Hi, I'm using BarTender 2016 R2 Automation.  So far, we have converted hundreds of labels from our old way of printing them to having them done in BarTender.  Huge difference. Very easy converting them.....so far. Like I mentioned, I personally have probably converted over 75 labels with no problems. We use the text file data source similar to this:

 

%BTW% /AF=C:\LabelTemplates\TMP229\TMP229.btw /D="%FilePath%" /PRN="Printer12" /R=3 /p
%END%
"00229M00229","327","ETL","CPN123","003"

 

And as I also mentioned, no problems up to this point. Now all of a sudden, I either get this line below to immediately show in the text field on the label that is assigned to the data source field, and/or it shows during the print preview. This is what the field1 data shows as.

 

%BTW% /AF=C:\LabelTemplates\TMP229\TMP229.btw /D="%FilePath%" /PRN="ProdZebra12" /R=3 /p

 

Also, when I'm setting up the new data source, it looks like it shows 3 records.  The first line (%BTW%) as one, the second line (%END%) as record 2 and the last as record 3.  But, It DOES recognize the correct field count from the last line. In the above it would tell me I have 5 fields...which is good. So, for some reason, all of a sudden, after hundreds of successful labels,it's breaking the text into 3 records. Just one label is driving me nuts!!

 

I really appreciate any help!!

 

Kurt
 

6 评论

0
Avatar
Legacy Poster
评论操作 固定链接

The first two lines are for the new integration part of Bartender (what used to be Commander).  When designing the label for the text database you should remove the first two lines.

 

The /R=3 in the first line tells BarTender that the data begins on the third line of the file.

0
Avatar
Legacy Poster
评论操作 固定链接

Thank you for your reply Slickson.

 

Yep, we know what the first two lines are for. We've designed several hundred labels this exact same way and this didn't come up.  It's really strange this wants to happen all of a sudden. I'll just keep messing with it.  Maybe I'll stumble on something or it will go away the same way it showed up. Just very odd. 

 

Thanks again.

 

Kurt

0
Avatar
Legacy Poster
评论操作 固定链接

I would expect the behavior you are experiencing if you are using a text file with the commander commands on line one and two.

0
Avatar
Legacy Poster
评论操作 固定链接

Not set what use to an a Commander Script type in 2016 yet but shouldn't the D= command be /D="%Trigger File Name%" ?

0
Avatar
Legacy Poster
评论操作 固定链接

Oh no I see it has changed to FilePath in the version.

 

When I am setting up the labels the data source I use only ever has the (in your case) the 5 text fields and I do not include the %BTW%....%END% command line stuff as this is only needed when Commander/Integration Builder is used to print the labels. The commands are added in as part of the triggering process at the start of the file used to automate the label production. 

 

With the command lines in place and printing or previewing in Designer itself I would expect you would see three records/labels as, I do not believe Designer itself "understands" the %BTW% etc. commands and needs Integration Builder to translate them and instruct Designer what to do.

0
Avatar
Rcusteau
评论操作 固定链接

How that issue was solved?

I have same kind of issue with a label having 2 rows per page.

The first 2 labels prints are containing part of the printing command that we don't see normally. All other type of label i did before that are working fine. only this one

 

Any idea?

 

 

请先登录再写评论。