I'd also hint at the loader Dragan already suggested. If any user has habit of running the app over weeks without reloading, you can add a check for new versions via timer or even force everybody out with the tools used when we saved "common data" serverside in dbfs and wanted to update the app/db structure and had to have all server dbfs closed.... ages ago ;-)

>>>Let me ask you a conceptual question (if this is also a violation of the owners' right, feel free to ignore).
>>>Say, your loaded put the EXE into the local drive folder. Then you need to update your EXE. You do that on the shared folder. But the user who has the EXE open from the previous loader session will not be updated until they close the app and open it again. Correct?
>>
>>Until they (all of those one user), reload the app, correct. But then nobody keeps the exe on the app server open, so you can copy it at any time. And if an user doesn't quit the app, well, she keeps using the old version. So they (all) soon learn to spread the news when the new version appears.
>
>Thank you. I will check out the download area of UT for these type of tools.