David,

There's not a good/bad answer to the question really, it all depends on what's happening.

If it's something that can happen asynchronously and it's independent then sure you could ShellExecute() to launch a separate exe and just let it work and go away.

Or you might need to launch it synchronously using the WSH.Run() method and wait for the exe to finish, but if you are doing this you might as well keep it as a regular method call inside the current EXE.

>Thanks, that works good. But instead, what about running another session of Foxpro to take care of the procedure? Good or Bad.