>Hilmar:
>
>I was restarting as the work around before I submitted the question.
>
>But eventually I found a solution that worked most of the time. Even though I could not delete the executable. I found that 4 out of 5 times that I could rename the executable.
>
>This allowed me to copy in the new executable.
>
>Eventually the renamed .exe's shut down so I could delete them.
>
>Mike Smith

I hadn't noticed before, but you should really consider using a loader program. That allows you to update the executable while the users are still working. As an additional bonus, users can go back to previous versions - this can often save you from going to the office off-hours for emergencies.

The basic principle is that every version of your executable has a different filename, to avoid conflicts: MyExe0001.exe, MyExe0002.exe, etc.

The loader program detects the latest version, and either (a) runs it directly from the server, or (b) copies it to the user's hard disk and runs it from there.

Solution (b) is preferred by most UT members, because it reduces network traffic.

Check the download section for "loader", so you don't have to write your own.