On 12/09/2014 08:21 PM, Lew Schwartz wrote:
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?
Thanks for the response, Lew.
Each PC has its own printer (and the printers are not shared over the
network) so only one job is ever sent at a time. The only thing that
ever gets sent to this printer is the label. My application is the only
thing that is run on these PCs.
--
Frank.
Frank Cazabon
_______________________________________________
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/[email protected]
** 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.
