>If you don't want users to run the EXE from their own hard disk, then you can >use a similar technique: The calling program calls MyprogA.EXE. When you have >a new version, you name it MyProgB.EXE, and change the calling program. Each >user gets the new program as they log in. Next program is C, then D etc.
>
>HTH

How will you code that ?. You are going to have the same problem with
the "calling program", am I right ?. Are you going to have the
calling program in something like C or C++ ?

This is what I do in few words :
I have a database with all the users of the application,
when a user starts an application, I track in that
database which application is been in use per user.
When I need to update an application I look in that database
the users that are using any application, then I send them a network
message asking then to close the application, if they don't
close in 5 minutes then the program force them to logout of the
network and then I can replace the file that I need.

Something else, I don't use big "EXE" files, no more, I split
the application in pieces, that way I can update the application
without stoping all the users from working. In example, I don't
include the report files in my projects.
HTH