Thanks, Ed. Clear and concise :-)

>WinExec() would work; it really ought to be replaced with calls to CreateProcess(), since WinExec() still exists only for backwards compatibility with Win16. There's at least one advantage to WinExec() or CreateProcess() in that you can control the ShowWindow state of the secondary process you launch; CreateProcess(0 offers considerably more control, and a means of tracking the launched application, since it returns a structure that contains the process id and process handle of the child process.