I was going to attempt the same report to file fix but suggested that the report be sent to another printer on the network to try and isolate the problem. The report prints fine to a LaserJet II with no other changes, just takes much longer. Strange. Seems like if NT was timing out the printjob it would do it to the II with 4 megs of ram rather then the 5 with 16 megs.

>I've been encountering strange printing problems on NT too. I have a small fpw26 app that prints reports in a scan loop. I have two REPORT FORM statements. One to the printer and one to a file on disk (in case a re-print is needed--glad I put that in there!). Sometimes not all the reports print, but the files from the REPORT FORM to FILE work. But there's no error about printing. It just doesn't print. It's a pier-to-pier situation. None of my Win95/98 clients experience this problem. I just have them send the file that's created to the printer as a work around when it happens.
>
>>Thanks for the insight. The printer that is being used is an HP5, don't know how much memory it's got. I'll be looking at it all more closely on Tuesday. Maybe then I'll have an answer (or more questions :)