>>WScript.Shell's RUN does work. (What do you think that means?) If I'm not mistaken though, this may not be a solution for a distributed app that has to run on God know what machines. Am I right about that? Isn't Shell32.dll going to be more or less universal in Windows but WScript is not?
>>
>
>Ed,
>
>First, the WSH is freely re-distributable. Second, the list of what versions of Windows install it is pretty lengthy. Check VFUG's September newsletter. Ed Rauh and I document there, in the introduction to the WSH article we wrote, what installs it. Third, yes, Shell32.dll is universal to all Win32 OSs, and the WSH isn't.
>
>I'm wondering if VFP isn't having a problem with Win2K environment. That's about the only explanation I can come up with that would explain what you're seeing. I've never had to provide the fully qualified file name. It may have to do with how protective Win2K is of that particular folder. Other than that, I'm clueless.

The only time I've seen this behavior is where the end-user frobbed the Windows search path by hand. ShellExecute() has 0 (nada zip, bupkus) control over the search path provided to Windows; the VFP path is completely independent. OTOH, frobbing the PATH environment statement can cause problems, and that's the only time I've seen this occur.