>>>>Hi,
>>>>
>>>>I opened a thread in ASP.NET forum on this issue. But these are VFP 9 questions.
>>>>
>>>>1. When the program executes REPORT FORM, is there a way to view it from the OS?
>>>>2. What would make REPORT FORM not executed at all? Ignored by the code (even though a tracer shows the program right before the REPORT FORM and right after)? And no error because the REPORT FORM is in the TRY/CATCH.
>>>>
>>>>I even eliminated the printer itself, changed the code to output to a text file. And when I run the program from a command prompt, the dummy report (with not data) goes to the mytest.txt file.
>>>
>>>You should be more specific ;-)
>>>I am guessing OS command prompt, not vfp command prom your existing log to point of failurept, but that alone can make differences it path resolution and so on. Also in/out of process should be cleared up, unless you call the vfp progran via shellexec ;-)
>>>
>>>>But when I call the VFP program from an ASP.NET program, the file mytest.txt is not created. So, something "happens" that make the REPORT FORM to be ignored.
>>>
>>>2 ways to continue: implement callbacks into report processing, continuing you current logfile. SWAG guess is your hunch of total report command failure is correct, in which case that setup would give no further info, so I'd make certain next that the report functionality works if called as COM object as is done by IE, best from a exe run from OS command prompt calling in your ASPNET-loadable COM component.
>>
>>In this application COM object is not involved.
>
>Then I am also guessing something permissions related and would wrap calling vfp exe with a batch file.
>But as your vfp exe seems to start right up to report command, then the hint about callbacks might work, starting with the data environment for the report and so on. Vfp9-report engine or oldstyle report ?

I will try putting the VFP exe into a batch file; interesting approach.
Yes, the report is VFP9 REPORT FORM.. I don't know what you mean by old style vs new stype. The report is not using data environment.
Thank you.