>>But again, if you want to keep it simple, you probably should just go with the Setup Wizard. By the way, how big a site are you dealing with?
>
>I tried the Setup Wizard, and it installed the EXE etc on the server, however, it installed the runtime files on the local disk, so the other workstations can't run the app off the server.
>

Bob, at least some of the runtime support files must be installed on the local machine (in fact, it's best that they all are, but at a minimum, some of the .DLLs and .OCXs need to be in the Windows System directory) so your best bet will be to create a runtime install separate from the application install, and place that somewhere on the network; your users can then install the runtime on their station as needed, and simply create a shortcut to the application on the network. The Windows Scripting Host would be an ideal medium to handle the task of creating shortcuts to the network copy of the application once the runtime files were in place, and in fact it could fire the runtime installer before creating the shortcuts. The WSH has an Automation Object (Wscript.Shell) that can handle the task of creation and maintenance of shortcuts quite easily; once installed on a system, the Wscript.Shell and Wscript.Network Automation objects are available to VFP as well.

>Any ideas?