>Thanks for your responses.
>Bruce, I like your idea of a launcher exe - seems a elegant way to handle the situation. I certainly wasn't looking forward to the idea of updating a dozen or more local versions every time I make a change!
>
>Thanks again...
>
>>Makes little difference on a good LAN in performance, but local is a little better. But the optimal solution for you is usually "both." The problems, as William was getting at, are:
>>
>>1) Updating local EXEs scattered all over
>>2) Updating the server EXE when it's being constantly used.
>>
>>The solution is a launcher EXE, which checks to see if the local version is older than the server version, and if so, copies the server version to the local machine, and runs it either way. Answers all the possible problems...

I run local exe's for 12 + users on our network. I have a simple update procedure that will update the local exe. My users have an icon to run that update and they get an email when they have to do an update.

This way I can update the exe as needed and then have my users update on their own.

__Stephen