I'll deny this if anyone asks, but we made a class for SetPrinter(cPrinterName), and trapped the error with the
class.Error method, and put in limited retries (up to 25 in our case). You'll notice that usually after 4-5 attempts, the
Set Printer will work. If after 25 attempts (so far never reached,) then the command set printer to GETPRINTER() is
executed, and the user picks the printer and proceeds with the report..

>>We've been using VFP SP3 with NT & Citrix for quite a while now, and you're not alone. We constantly receive
>>Error Loading Printer Driver, we finally had to resolve it by putting the SET PRINTER .. commands in a loop and
>>if it can't set it after 20 or so times, then error out. It's ugly, but MS/Citrix/FoxGroup no-one seem to be able
>>to fix it up.
>
>
>Sorry ... i have some difficult to undestand your solution (my english ..).
>
>With your loop, you detect the error programmaticcally ... but you have not solve the problem ... or not ?
>
>How you assure that the report work fine ?
>
>Thanks again!