>Why do you want the EXE on the server? Does it require specific server resources?
>
>Even after deployment, this app is going to be updated on a daily basis. I just thought that it would make updates easier, that's all. Plus, there are abount half a dozen guys already using the app and their shortcut is pointing to the exe on the server. I don't want to confuse them :)

You could be sneaky and replace the exe with a loader of the same name that pulls the most current EXE to their machine and starts it.

That's basically the way my larger VFP apps worked. I had a build process that gave each build a unique name and dumped it into a production folder. I had a loader EXE that grabbed the latest EXE from the production folder to the user's PC and ran it.

That way you could make a new build w/o tossing users. Users would get the new build when they restarted the application.

Running locally made a serious performance difference.