>(1) Because if they wish to install the app on another computer they will then first have to install the old version
>
>(2) Our distributers would prefer to get a single disk upgrade (say disk 4) rather than a whole new set of 4 neew disks. Time wasted in copying etc.

If the EXE, data, and other files for the app reside on a server, then you could achieve a one disk distribution. The majority of your distribution disks are now the VFP runtimes, ODBC drivers, etc. that are included in the standard Setup Wizard configuration. Not one of those files changes with a change in your VFP code...

I have seen many posts here concerning your business problem. You may want to consider creating a small EXE that calls your actual program on the server. In this way, you can make a distribution set of disks for a one-time install to any client workstation that would access EXE on the server. To make your program even more modular, you could exclude forms, class libraries, and reports from your EXE; in this way, a change in one form or such does not mean a recompile, simply a copy of the new form sent to the client site.

HTH,

Jack Mendenhall
Reinsurance Management, Inc.