Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
RUN, ShellExecute, WinExec, CreateProcess bad starts
Message
From
17/08/2010 13:54:35
 
 
General information
Forum:
Visual FoxPro
Category:
Windows API functions
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows XP SP2
Miscellaneous
Thread ID:
01476859
Message ID:
01476863
Views:
212
A directory name with spaces in it?

>Hi,
>
>I have sucessfully launched an external windows program from a menu button in a vfp application for years on many types of computers running many different OS's and SP's. Last week I install the same vfp app on a dell optiplex 780 running windows XP pro. When I hit the menu button to run the external windows program the external program opens and then closes after 2 seconds.
>
>I have attempted to launch the external windows program using:
>1)run /n
>2)run
>3)ShellExecute
>4)WinExec
>5)CreateProcess
>
>All gave the exact same response. Namely: the external windows program opens for a moment and then closes. At the same location, (all serviced from same firewall with virus and spyware shut off) I installed the program and external windows program on several different computers. It is only one computer that is experiencing the problem.
>
>I then substituted notepad.exe for the external windows program. THAT WORKED FINE on all computers including the one in question.
>
>I then wrote a 1 form vfp program and compiled into an exe. That program was able to run the external windows program just fine on all computers.
>
>So the problem is specific to my initial vfp app installed on a particular computer. Everywhere else it is installed it operates fine.
>
>I even had my vfp app run a vfp app compiled into a dll and a vfp app compiled into an exe which launched the external windows program and that did not work either. I also had my app run a batch file that runs the external windows program and that did not work either.
>Today I created a .net windows form app that launched the external windows program just fine. BUT... when I had my vfp app launch the .net app the same symptoms occured.
>
>Any thoughts? What might be missing from this computer. What might be running on this computer.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform