Hi Sergey,

The report program actually finishes what it is doing so I don't think it is stuck in a loop. As well, the file size in the spooler (I have checked) does not grow any larger than usual - which is what I think would happen if VFP was actually generating lots more pages - it's like the spooler is not closing the job / releasing it or maybe there is some sort of "copies" setting in the spooler that is getting messed up.

Albert

>Maybe loop variable gets modified/reset by report?
>
>>
>>Users of an app of mine do a lot of printing of reports such that they want to check off say, 6 proposals of 3 copies each (legal stuff) and have them go to their printer without having to a) wait for them all and b) have to set the copies on their print dialog for each report.
>>
>>I have accomplished this by offloading the report generation to a server where an app on the server checks for reports to be done and then loops the requisite number of times through all the reports.
>>
>>Works *most* of the time but the latest problem has been that every now and then, they will one of the printouts generating dozens of the same report until the printer runs out of paper - when they only asked for 3 copies.
>>
>>Examining the print queue, it does not seem like VFP generated hundreds of pages because the print job size is not that large - it either seems that VFP has not "closed" the print job or somehow the server queue software has choked and it is reprinting the same job over and over.
>>
>>I have tried getting the latest HP printer driver (HP 2430n PCL6). I have tried going to a "simpler" HP driver (HP 2430n PCL5e). I have tried using the HP 2430 post script driver - all to no avail. If it means anything, the report *has* to use the new print mechanism since the report needs to use a report listener.
>>