>>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?
>
>This morning I placed the program PrintOrder.exe and all the configuration files (.xml files) to the ASP.NET application BIN folder. And the program seem to have started printing (the customer will soon confirm). So it must be some kind of the folder access privileges issue. I actually tried to play with the security settings of the "original" folder where PrintOrder.exe is supposed to reside. But nothing worked. It means that I am not 'hitting' the right setting.
>Leaving the PrintOrder.exe in the BIN is not a problem but could be maintenance issue since sooner I later it would have to be updated and it would have to be done in two places.
>If anybody can suggest what Security setting could be 'holding' the ability of PrintOrder.exe to print, please let me know.

Even though the printing works, I noticed that in the Task Manager (on the server) there are as many instances of PrintOrder as the times it was fired from the ASP.NET application. I am concerned that eventually this will be a problem. I need to find a way to run this PrintOrder but not to add it to the server process on every run.