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.