Hi,
Apparently the report for whatever reason fires the piece of code in the driver that has a bug in it. The rendering routines in printer drivers vary greatly both in there efficiency & robustness.

Update one workstation and see what happens.

>But why then do all of the other reports (hundreds) print fine to the same printer?
>
>>Hi,
>>I had a similar problem today, the printer drivers needed upgrading.
>>
>>>We have an app that is running at literally hundreds of locations. At one site only, they have 5 workstations (all Windows XP) and each workstation has its own HP PSC 1200 series printer physically attached via USB. Our app has many reports - some are created using the report generator and some are @...say reports. None of the @...say reports send any escape codes to the printer. All reports prints EXCEPT one report. The report that won't print has two versions the user can choose from: an @...say version and a report .frx version. Neither will print. Everthing else, literally hundreds of reports, print fine. When the user at any of these workstations prints either of the two versions of this report, the report goes to the print queue and then windows generates the error message:
>>>
>>>"Foxpro user defined job: Document failed to print."
>>>
>>>The print job either never hits the print queue or is deleted so quickly that the user never sees it in the queue. The HP PSC 1200 series printer is a GDI printer, but I have tested the same report (in both versions) on many GDI printers and both versions print fine.
>>>
>>>Any ideas?