Thank you to you and Naomi, now I will know. :)

>Yelena,
>
>jut a sidenote. I you add # between the word Thread and the thread number, and between the word Message and the message number, UT will create links automatically. Thread#976797 and message#978275
>
>>Well,
>>Your user will be able to continue using your system without waiting for the print to complete.
>>I found an original thread that I posted in 2005, you can check some drivers suggestions maybe they will help in your case, they did not in mine. The thread number 976797 and the message id 978275
>>
>>
>>>I am ok with outsourcing the actual print job to another process but we need to wait for the printer anyway, right?
>>>
>>>>I can appreciate that and that is why we created a separate EXE file to print the labels which would let the user to continue working in the system without waiting for the print to complete.
>>>>
>>>>
>>>>I checked our code and we used the following command to execute an outside EXE.
>>>>

>>>>RUN /N7 PrintLabel.exe <list of your parameters here>
>>>>

>>>>>I cannot possibly think to wait between labels for 7 sec. What ever time it takes to print a label is already too long :). We print thousands of labels every day.
>>>>>
>>>>>>We had a similar problem with Zebra printer. We were still developing with VFP8 at the time. In our case that sometimes without user’s interactions some random labels got skipped.
>>>>>>We experimented with it and found that if print one label at a time with a pause in about 7 seconds in-between the problem went away, but we could not afford to make our user wait that long, so we created a separate exe for the label print we create a cursor with all the labels ready to get printed, converted this cursor into XML file and pass the name of this XML file into the new EXE file calling it using windows shell API. This way the user can proceed with their task while the print task was still printing the labels. I know it is not the most elegant or best of solutions, but it is working. I would be interested if you or anyone else can find a different way to deal with it.
>>>>>>Here is what the code in the "printing" exe looks like
>>>>>>
>>>>>>

>>>>>>
>>>>>>=XMLTOCURSOR(lFile,"ZPrintLabel",512)
>>>>>>SELECT ZPrintLabel
>>>>>>= AFIELDS(laReport)
>>>>>>LOCAL lcLabelCursor, lnSec
>>>>>>lcLabelCursor = SYS(2015)
>>>>>>CREATE CURSOR (lcLabelCursor) FROM ARRAY laReport
>>>>>>SELECT ZPrintLabel
>>>>>>GO TOP
>>>>>>SCAN
>>>>>>	SCATTER MEMVAR MEMO
>>>>>>	SELECT (lcLabelCursor)
>>>>>>	ZAP
>>>>>>	APPEND BLANK
>>>>>>	GATHER MEMVAR MEMO
>>>>>>	LABEL FORM (lLabelForm) TO PRINTER NOCONSOLE
>>>>>>	lnSec = SECONDS()
>>>>>>	DO WHILE SECONDS() < lnSec + 7
>>>>>>		** the printer need some time
>>>>>>	ENDDO
>>>>>>	SELECT ZPrintLabel
>>>>>>ENDSCAN
>>>>>>

>>>>>>>I have a program that prints labels with barcodes on Zebra printers.
>>>>>>>The user has two printers attached to a computer where she is running two copies of my program.
>>>>>>>Printers are different models, using different drivers but both from Zebra. The user has been reporting to me that when she pauses printers due to media change or any other reason one of the printers will not print all labels. Longer printer is paused more labels to lose. The labels are just a VFP report with a custom page size.
>>>>>>>
>>>>>>>Any thoughts?