>The report is in two versions already. One is a .prg using all @..say to send the report to the printer and the other is the vfp report .frx. Typically, when all else fails, the user will select the .frx report (especially for GDI printers) and that will always print. At this location though, the workstations all have the same printer and neither of the reports will print. I have verified that there is no specific printer information in the frx just to make sure. None of our users anywhere else have that specific printer for testing or comparison. Yet all other reports in our work print fine...
>>>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:

Then it sounds like there is corrupted data in your report, sending a bad command that the printer driver is interpreting incorrectly. Send the output to a file and compare it to a known good report. Maybe just look at the data that's being sent to the report by browsing the info first?