× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We're going to be printing 1000+ labels as a batch for batch warehouse
picking.  If it jams on label 862 (and someday it will), I certainly do
not
plan on reprinting those first 861 good labels.

All of the Zebras we have in service recover to the last label printed
whenever they jam, run out of ribbon, etc. There is no need to resend
the entire spool file, or any part of it. It'll patiently wait until we
correct the media flaw then resume where it left off.

And I don't see where that's the fault of the "generating
application/procedures are forcing it be an issue.  (In which case they
can
and should be changed.)"

Well, for starters, why generate all your labels in one monolithic spool
file? I can't think of a compelling reason myself. 

We generate between 6-10,000 labels a day and don't do it that way, and
incidentally have never had any reprinting issues in 7+ years of
continuous operation, remote outqs, lack of page range support and all.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.