>>Does anyone know why this is happening?
>>
>>On a users machine, if I try and run my exe from the network (our file server which is in the same domain as the user machine) I get the message: File "whatever.exe" does not exist.
>>
>>If I copy the .exe and the two .dll files to the users hard drive and then try to run it, it works fine.
>>
>>Why can't I run the program from the network?
>>
>>Thank you for any input.
>>
>>Ryan
>
>How did you add the shortcut on your desktop? Manually or using the wizard?
>If manually, possibility of missing the proper path of the exe or folder access rights of the user.

A frequent cause of this behavior is a target path containing an embedded space pointing to the .EXE; if it is pointed to by the file's shortname (legal 8.3 version of the full path/file name, retrievable using the Win32 API or Scripting.FileSystemObject File Object) the problem often goes away. The most problematic situation is in UNCs where either the machine name or share name are the source of the problem; these cannot be abstracted to valid 8.3 names (a machine's name and its associated shares can't be shortened or legalized; an NT system with a machine name of \\NT SYS1A, with a share called "C App Dir" has a fixed UNC of "\\NT SYS1A\C App Dir" unless you change NetBIOS names for the machine and create a new share with a different name) without mapping the UNC to a local drive letter, after which a short name can be constructed.