I had this many years ago on a VFP6/early windows systems. I don't think I ever chased down the cause, but some combination of explicitly setting the printer off and/or sending a cr after the print job seemed to do the trick. Another issue might be a page length setting persisting from a different job. How do you prevent multiple printers from accessing the printer at the same time?
-Lew Schwartz On Fri, Sep 12, 2014 at 3:57 PM, Frank Cazabon <[email protected]> wrote: > On 12/09/2014 03:45 PM, Koen Piller wrote: > >> Set a catch .. End catch to catch your Errorlog in printagreement and also >> in your printlabel procedures >> Koen >> >> >> > Thanks Koen, > > I already have an error handler (the application's) in place but I'll add > a TRY CATCH around just this bit of code and see if it catches something > the global error handler isn't. > > -- > > Frank. > > Frank Cazabon > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cafuu78dzoyutkhuhculhb7lf0ufrkwgpnvvsu-_owlm35fe...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
