>>Hi,
>>
>>I have code in my ASP.NET that calls a VFP9 program that prints a one-page report. This program works on my computer and works on one customer's server. The code is as follows:
>>

>>Process.Start( "c:\\appfolder\\printorder.exe", nOrderNumber.ToString()));
>>
>>

>>
>>But when I introduced this change to one other customer, it does not work. I see on this customer's server in Task Manager that the process Printorder.exe starts every time I run the application. But it does not do anything. As if it hangs on instantiating or something. I placed some "test messages" in the Printorder.exe but they are never fired. And after I close all these processes in the Task Manager and run the ASP.NET app again (which starts the printorder.exe), the server appears in the Task Manager but nothing fires.
>>
>>What could be stopping this process on "this" customer's server?
>
>Presumably some difference in configuration/permissions. Don't know if this might give some clue :
>
>https://msdn.microsoft.com/en-us/library/system.diagnostics.processstartinfo.errordialog(v=vs.110).aspx

I will try to call the Process differently, using UseShellExecute, as the article you linked suggested. I also plan to try to place the program PrintOrder.exe right in the BIN folder of the ASP.NET application. Just to see if it makes a difference.
Thank you.