Skip to main content

Search

Search

Error #304001 Exporting Printer Code Templates Error

Comments

6 comments

  • Avatar
    Ian Cummings
    Moderator

    This is disabled in the trial edition as the error message states.  You will need to use a fully activated license of the Automation edition or higher.

    0
  • Avatar
    Legacy Poster

    Hi Ian,

    Thanks for your help this option will upload zpl file to the printer?I have a college using ultra edition and uses the run btxml option to upload the zpl file to the printer 

    can you help me with steps to do so with this trial version

    0
  • Avatar
    Ian Cummings
    Moderator

    The Ultra Lite edition is the freebie edition that comes with particular printer brands.  It does not support the exportation of Printer Code Templates which is what you are referring to.  BarTender XML script is an entirely different thing altogether, it is a scheme of XML that BarTender natively understands and is used to direct BarTender to open a particular document, choose a particular printer, set data on the label and then print.  This is not an XML that gets sent to any printer whatsoever.  See the following Help topic that explains what BarTender XML script is: http://help.seagullscientific.com/10.1/en/#../Subsystems/BTXML/Content/Overview.htm

    0
  • Avatar
    Ian Cummings
    Moderator
  • Avatar
    Legacy Poster

    Thanks Ian ,

    I read the pdf,so I guess i need licensed version to export to Zebra printer but please bear me in my next question all i need is to print the label from the oracle mws

    so if I used exporting template form the designer my label will be uploaded to the printer and i can print it directly or i need the commander?

     

    thanks and sorry for asking too much 

    0
  • Avatar
    Ian Cummings
    Moderator

    Yes a fully licensed BarTender Automation edition or higher is needed in order to produce Printer Code Templates (PCTs).  The idea of PCTs is that you use BarTender as a design and printer code export tool.  The PCT would then be embedded into the "system" or the printer, and then recalled and merged with variable data at print time.  Note that BarTender is not in use at print time with PCTs.  Disadvantages of this approach include limitations on the type of label objects used (device fonts and barcodes only, advanced text formatting that reacts to variable length data, difficulties in maintaining embedded print files, and being stuck with one printer brand, or even model, per PCT file.

     

    Using Commander on the other hand means that BarTender will be used at print time, thereby giving you the full power of the BarTender print engine to print whatever you want to whichever type of printer, while allowing you to easily integrate with other systems with the need to do any programming.  I suggest you view the below white paper for more details: http://www.seagullscientific.com/label-software/whitepapers/overview-of-commander-new-201406.pdf

    0

Please sign in to leave a comment.