Even the simplest test does not work. For example, inside the COM DLL, I try:

cAppName="C:\TestDir\ZIP.EXE"
RUN &cAppName

Something like that. But the EXE won't run. This example is very close (in a much simpler form)to what I'm actually trying to do with a command-line Zip utility (from info-zip).

I know that the COM server is working. I have methods in it that access specific ASP objects (i.e., request, response, etc) and actually generate functional web pages. But I cannot successfully spawn an EXE from within the DLL.

>Mark,
>
>You said you provided the fully qualified path name for the executable, was it written as UNC? Inside your EXE, are all your file references written as UNC (for files not included in the project)? If you are using any mapped drive instead, it will cause problems for the drives will not be mapped, then you need to use UNC, or map them again in your app.
>
>>I have run into problems when trying to invoke an EXE from within a VFP COM server that is being instantiated by an ASP application. For example, something as simple as "RUN xxxx" where xxxx.exe is something that normally runs fine at the command prompt. It won't work for me. This even when I provide a fully qualified path name for the executable. I don't understand why it's failing. Is it because of restrictions on the IUSR_ account? Or is this a limitation of VFP COM servers? Any info appreciated. Thank you.