>What are the exact files (and their distination location) that must be installed on a machine in order to run a VFP 6.0 .exe file?
>
>Whenever I added a new machine to our network, and wanted to run a VFP5 .exe file, I only had to copy a few files into the \windows\system folder and she would run. This prevent having to go through the Setup Wizard to install a simple app.
>
>The app uses only basic sub-classed objects, no ODBC, no ActiveX, and all the data, forms, and reports are accessed on a common foled on the network server.
>
>I just want a quick and dirty way to get a new maching up and running.
>
>Are there any negatives to doing it this way? Is this going aroung the registry going to cause any problems, or should I use the Setup Wizard like a good boy?

The minimum files and file dependencies are outlined in a file in DISTRIB.SRC - VFP6R.DEP. I strongly advise against trying to just copy the files in place, since many of them update common components that are already present on the system and may be memory resident, and others must be registered on the system. In the case of files requiring registration, the registration must occur after any other .DLLs needed by the file being registered have been copied in place, and in some cases registered.

Dave made a solid recommendation - creater a minimal runtime install using Setup Wizard, and use that to deliver the runtime environment. it can be called, silently if you like, from another installer. it takes the headache out of the worst of the install process. You'll also want to consider the issue of DCOM components; see my FAQ entry on what indicates the need for DCOM components to be installed on the system, and what sources you can use to install them.

After the runtime is installed, you can simply copy your executable and data files, and do whatever you like as far as creating shortcuts, etc. I strongly advise installing the Windows Scripting Host along with your application; there are several OLE Automation objects included with it that make some rather annoying tasks, like programmaticaly controlling the creation and modification of shortcuts, very easy, and serve as a mechanism to make the strength of scripting with VBScript of JScript available to you for installation and within your applications.