>Yeah, there could be one user running ACC001.EXE, one running ACC002.EXE, and one running ACC003.EXE on a day that I was a busy beaver and was puting more than just one update out on the network. There's really no limit. As the users shut down their computers at the end of the day and start up the next day, then, of course, they all end up on one EXE again. I have an auto-shutdown routine that will force users out when data structure changes are needed or some other event requires me to have exclusive access.
>
>>Update:
>>Understood finally I hope <vbg> ;
>>Can be done with 2 exes at the time only;
>>You send acc_002.exe and while users stil have acc_001.exe loaded already, when some user log out and then back inn, loader simply launches 002 for him by comparing version#. Latest version# is automatically stored somewhere in server data. Eventually some cleanup routine wipes out older versions...
>>There is no exe overwriting going on, there4 there is no problem.

This is just fine :)
Probably you have some small app taking care of version / numbering etc.

In my case loader is somewhat 'hevier', more then just a loader. It also
downloads latest templates from server to user machine, switches between various modules (exes), checks for exe (agetfile)version, does loginn, writes into ini-dbf and so for. You drop exe on the server and that is it.
I use excel and other templates heavily, so that resolves my problem in this area as well. Every user have his own set of tempates localy. Again you drop template on the server it gets picked up whenever exe version changes, and so for.
Back side is that you have to install it once on each machine (I did full installation everywhere), but after that you get some nice advantages out of it. I never considered network traffic as real constrain or reason
to do this kind of setup, but was more after those advantages.
PC's / networks are flying nowadays. I do not believe we should really account for each nanosecond, when we are doing more less the same things we did back on that 'Turbo-AT386/40mhz thunderbolt' :))