David,

If I create a shortcut to a file, then move the file to another folder (using Windows Explorer), double clicking on the shortcut will still open the file (which is now in a different location). It is interesting to note that if I visually inspect the shortcut immediately after moving the file, it still appears to point to the original location (which does not exist). After double clicking on the shortcut, the target is changed to the new location.

I would suggest you employ a launcher. Nick has one in dowloads, let's see...download #9668. Your shortcut will point to it, and it will never move. You will be able to update the .EXE on the server without kicking folks out of the program, and most current .EXE will run from each persons hard drive.


>Have you ever seen this happen:
>
>You create a shortcut on a workstation, which launches an exe somewhere on the network.
>
>Then the day comes when you need to move an enhancement live. So you move the exe to an archive folder and replace it with a new exe.
>
>Only trouble is, the target in the shortcut now points to the exe in the archive folder--not the new exe.
>
>This doesn't happen all the time. But I know I've seen it happen before. In fact, it recently happened to one of our client's IS staffers--and he swears that we modified the shortcut's target manually.
>
>Can anyone shed some insight into how to replicate this behavior?
>
>TIA