Hi Krishna,

Eric has provided an excellent working example. JFYI, you may use CreateProcess to launch the executable. This API will return a open handle to the new process so you dont have to open a handle. It also gives you better control over the creation process that VB's Shell does not.

Also, remember to handle all errors that may be caused in Windows API procedures. You can do this easily by using Sunlet Windows Error Services, a free component available at http://www.sunlet.net/products/WinError.htm.

Regards,
SUN.