>Hey Ed,
>
>Just a quick question, I'm just curious ...
>
>>You'll need to create a .PIF file for the batch file, that specifies Close After Exit, and then execute the batch file using something like the FFC ShellExecute class (uses the ShellExecute() API call) or my API_APPRUN class (uses Createprocess()) rather than RUN.
>
>What exactly is the difference between the two?
>

A lot, mostly involving what can be run (CreateProcess() can run an executable of any sort, ShellExecute() can run an executable or launch a document with it's registry-specified application associated with a command verb like 'Open' or 'Print'), how much you cna view an control the executable (CreateProcess() returns both a ProcessID and a Process handle, which lets you do lots of things), and what things you can control at launch (there are two structures in CreateProcess() that can control an amazing variety of things like DOS environments, shared handles and the like, not available to ShellExecute()).

For what most people are doing, unless waiting on temrination is a major issue, theu can both be used. If you need to get a return code or monitor the run status, you need either CreateProcess(), or ShellExecuteEx(), a ShellExecute() on steroids. When it boils down to it, ultimately, everything relies on CreateProcess() to spawn a child process.

>-Bonnie