I've been bitten by this one. If you move or rename the target and then before you install your new target the user clicks the icon, Windows will search for an instance of that target and if it finds it, much to my surprise, will not only run it but will modify the shortcut! There is a message to the user "Searching ..." but depending on how far away the other instance is that may not be on the screen for long before the app comes up. Suggest renaming archived exes.
>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
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
