Hi Pascal.

I know of three options:
1) EXE on server
- everyone gets updates at same time
- must wait until all users are off to update exe
- easy to admin
- no installation except VFP runtime on pc
2) loader EXE on each workstation. This EXE checks for a newer program EXE on the server. If it is newer it downloads it to the local harddrive.
- next time someone runs your they have the latest app
- can update the EXE on the server at any time
- more complexe to admin, loader EXE might have problems
3) EXE on local pc
- no really an efficient option
- update to EXE requires programmer to visit each station

I prefer option 1 since I can't always trust that I have permission to copy anything onto the local pc.

>I was wondering where you put the VFP executable when used in a network : on the network or on each client ?
>
>My problem is : I have an application still under development (which application isn't ?) with very regular updates. It's on the networkdrive, so if I want to update i need all users to quit before I can update, or wait when noone's there anymore.
>
>I'm curious about your elegant solution ...
>
>The workaround I'm thinking about is : have the application on the localdisk, and each time the application is launched, check if the application on the serverdisk has a later date. If so, quit and let the user with a separate updater (which is actually a simple copy program) update his local copy of the program.
>Pro : quick and easy : no more executable is in use anymore
>Contra : what to do when the database is updated together with the executable (which doesn't happen as often as program updates). In this context would it be nice to be able to give the DBC some kind of version number that you can check the program's version against.