Yes I use this approach too, but instead of relying on timestamp/size I prefer to keep version number in database.

>Another alternative to the two solutions listed below is to include a program on each user's local machine that compares the local .exe's timestamp and file size against the executable on the server, and if there is a difference on either check, the program will delete the local .exe and copy down the network .exe.
>This way, you only have to replace the network .exe and you save yourself a lot of footwork and support calls.
>
>>Afterwards, if you make some changes in source code, you have to rebuild >executable on your development workstation and copy it over to all client >workstations. You can also put executable on server and give users shortcut >there to launch application. It will make replacing executable easier, but >it's not the best way (IMO).