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:
>>
>>"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?
>
>Tracy,
>
>Not many, but the one that comes to mind is a difference in driver versions.
>
>OTOH, is there any reason why the report couldn't be converted using the native VFP report? I've done a number of reports that seemingly couldn't have been done with it.