>>>>On top of my head:
>>>>1. You are never be sure that Windows Scripting host is installed. ShellExecute is Windows API and it is always there :-)
>>>>2. With WSH you could Run the other application and WAIT until it is closed.
>>>
>>>Thanks, Borislav. The question is: why Shell.Run worked and ShellExecute didn't?
>>
>>I should read whole thread :-)
>>I have no idea why.
>
>I'm starting to doubt what is the correct expression in English.
>
>"I should have read" the whole thread or "should read" would work the same way?
>
>As for 'why', may be Srdjan used 'Open' parameter? Just want to understand the difference and when should we prefer one method as opposite to the other.

O! Don't doubt at all. Check what I used and the opposite is right :o)

I prefer to use ShellExecute. As I said You are never be sure that WSH is installed. Some SysAdmins remove it for "security" reasons. I am tired to argue with them :o)