This might happen when the .frx contains a printer at design time. The report then tries to print to the printer defined at design time. Well it did that 150 years ago. :)

>>>Hi,
>>>
>>>I have a routine where the ASP.NET application executes a VFP 9 application (exe file) which connects to the server, finds a record and then prints it as a report. This routine works for many customers.
>>>
>>>But I run into this one case where the VFP application executes but nothing is printed. I did the following tests:
>>>1. When I run this executable from the command prompt, it works, the record is printed.
>>>2. I have test code in the executable that writes a log of various points in the program. When the executable is run from the ASP.NET application, the log is completed; all points. The point of connecting to the SQL Server, finding a records, etc. One point is specifically right before the command REPORT FORM ..... and the log has this point. But the REPORT FORM prints nothing.
>>>3. I created a dummy report, that has not data. Simply says "Test Report". So, I REPORT FORM this dummy FRX but it does not print either.
>>>
>>>Any idea what maybe missing?
>>
>>Description of print target: file, file+email, actual printer ? Printer connected/turned on ?
>
>Print target is a printer, nothing special. The code is almost exactly as below:
>
>

>SET printer TO NAME (cPrinterName)
>REPORT FORM "WorkOrder.frx" next 1 NOCONSOLE NODIALOG to PRINTER
>

>
>I verified that the cPrinterName is correct since I placed a bunch of "points" within the program, saving various conditions to a log.txt file. So I see which point was "hit" and the value. And as I mentioned above, the program works if I execute it from command prompt. Only when I execute it from the ASP.NET application, all works except printing.