>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

The following may be the reason. If at any moment the executable doesn't exist, or isn't reachable (insufficient rights, not network connection), and the user double-clicks on the shortcut, Windows will kindly search for the "closest match", and assign it - sometimes without asking for confirmation.

The solution might be to keep a backup of the shortcut somewhere, and overwrite the original.

HTH, Hilmar.