Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Run batch file
Message
From
25/09/2002 15:45:24
 
 
To
25/09/2002 15:24:14
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Windows API functions
Title:
Miscellaneous
Thread ID:
00703275
Message ID:
00704454
Views:
19
>>Hi,
>>Thanks, I filled the fourth parameter and it works.
>>It seems better to create Process than using ShellExecute. Am I right ?
>
>You'd have to ask Ed about this. From what I remember the last time he answered this question, CreateProcess gives you more control than ShellExecute. Most of all, I like the ...AndWait part.

ShellExecute() actually invokes CreateProcess() once it figures out what to launch; ShellExecute lets you launch a doc and trigger its associated app automagically via the registry; using CreateProcess() gives you back handles and IDs for the created process and thread, allowing you to track execution and operate synchronously (VFP is blocked until completion) or asynchronously (VFP runs in parallel.)
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform