First Bartender label - help please

Yahoo Archive
1
I had the same problem in Crystal when printing labels in Vantage. The
fix for me was to set the zebra as the default printer before processing
the report in vantage.



It's a pain, but worked for us.





[Non-text portions of this message have been removed]
2
Bruce,

We have been using BarTender for several years. Mostly the same as you describe, enter job number or other info and use ODBC to get the data on a label.

Even though we are not using BarTender for this, we have been successful with the Print Tag button in MES. (8.03.404B) I would be willing to share my Crystal file for our Zebra printers.

We are using BarTender to autoprint shipping labels based on a checkbox on the Packing Slip. Support was able to walk me through this easily. You should try contacting a guy with the last name of Harris. First name begins with W. He did a webex and was very knowledgeable.

Sorry I can't get you though the exact steps. When I set up my autoprint labels, I used the .btl file data (after first printing the default BT label from the system) from the mfgsysdata\bartender folder. I renamed as .txt file and stripped the first two lines out. Saved that file as .txt in the same directory and used the Database Connection Tool in BarTender to bring in the data fields.

Hope this helps,

Doug Oswald
MIS
FLEETWOOD FIXTURES


--- In vantage@yahoogroups.com, "cooner_55421" <cooner_55421@...> wrote:
>
> Hi,
>
> I want to be able to print a Bartender label to a Zebra printer.
> This will be for the shop employees from within the MES "End Activity" screen. I'd like to use the "Print Tag" button there.
> I have a copy of the report data definition MtlTags that returns all the correct values.
>
> Can anybody explain the steps they would use? I am totally new to Bartender. For now I am setting one up a Bartender label using ODBC and a person has to manually enter the job number. I'd like them to just have to print the button and the job number gets passed automatically.
>
>
> Thanks,
>
> Bruce
>
> BTW....
> Below is the history behind this.
> Sort of a rant against Epicor I guess, sorry, but it's true.
>
>
> I modified a style but it would not format consistently.
> I tried to get a label to print correctly on a Zebra printer for over a year without success. For some reason, Vantage modified the print job and all the left margin moved to the center of the label and the right margin was off in space.
> After a year of back and forth with Epicor support, I was finally told it won't ever work and to get Bartender.
>
> Now that I have Bartender, nobody at Epicor seems to know how to explain how to set up a label. Especially from within MES, End Activity.
>
3
I have been able to use the standard data definitions for my labels.

We use 4" w x 2" h labels.

Not sure about the /rpt switch, but we did mess around with our local settings to get the labels right. But now that we have the settings, the labels print the same from Vantage or BarTender, correctly.

One more thing to try, use the Seagull driver and NOT the Zebra driver.

--- In vantage@yahoogroups.com, "cooner_55421" <cooner_55421@...> wrote:
>
> Hi Doug,
>
> >
> > Even though we are not using BarTender for this, we have been successful with the Print Tag button in MES. (8.03.404B) I would be willing to share my Crystal file for our Zebra printers.
> >
>
> I'd like to know about your Crystal file.
> Does it require a custom data definition too?
> We are using 3" wide x 2" high labels.
> Anything bigger will not work in our warehouse.
>
>
> A person can make 50 unique parts a day here so entering the job numbers is getting tiresome.
>
> Unfortunately every label I've printed from Vantage has the same problem here.
>
>
> I have Crystal files that print correctly from Crystal.
> When I print them from Vantage, all the text moves over about 1-1/2 inches.
> Apparently Epicor has a /rpt switch for clients to force local print settings that can overcome this.
> Unfortunately I'm still on 8.03.305 & the switch isn't available on this version.
>
>
> Thanks,
> Bruce
>