Well, that's not exactly how it works. There is a loader program that starts the latest copy of the EXE. Specifically, LAUNCHER.EXE is what the user runs and LAUNCHER.EXE looks for the latest copy of PROGRAMNANEnnn.EXE and runs that. So an update during the middle of the day is just a matter of dropping the new version of PROGRAMNAMEnnn.EXE (with the number being 1 higher than the existing number) onto the server. If it's something someone needs, they can exit the app right away and restart. If not, they just get the latest version whenever they happen to exit and restart.

The bottom line is this: I started this technique quite a number of years ago now. It's hard to remember the exact thought process that went into it, however it works, I've never had a complaint about it, and it make for less fuss with the workstations and more control from a central spot. I have no problem with someone making a decision to load the EXE locally. I do think this is an area where it is acceptable for us to find what works best for ourselves and our clients.

>So you wld do what Russel did, and simply mail them updates which they are to 'post' on network themselves at evening and tmrw morning everybody would be up and running.