>>The story continues... I got the share renamed from "D drive" to "D_drive" but it still wouldn't work as long as I had spaces in the path (which it was willingly allowing on a local drive). So it seems to be spaces in an UNC path are a mortal sin (your exe does die, doesn't it?) and they're still OK if you have a drive mapping or a local drive (tried and both work, including spaces in path and in the name of the executable).
>
>You can always retrieve the file's ShortName using the Scripting.FileSystemObject or API and use that in the ShortCut.
Not that easy. The executable actually launches to a point where it gets the runtime to load, and then you see the runtime's window showing up, and then when it's about to execute some of your code, it says "File
not found". So, from what I figure, the exe's loader locates the runtime, but then can't locate itself anymore.
