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.