Hi Evan,

>Does a VFP developer need to know which files to include in the install (VFP runtime files too) and also know where each of these files go? For instance would the developer need to know VFP6RENU.DLL needs to go into the Windows system directory?

There is no template for VFP, we still have to know which files to include and were to put them.

>Perhaps this is the answer to the above question. We only need to figure this out once then?
>

This is true but there is still a lot to learn about how to use the .msm files. I originally created one for the VFP system files and tried to put it in the winnt\system32 directory. It installed as a single .msm file, not as the individual files included. I ended up removing the .msm and directly assigning each of the VFP files to the winnt\system32 directory.

>From what I understand, Windows with then repair the install if one of the DLLs goes missing. Does each workstation keep these dlls or are these stored in a network location.
>
Copies of the files are embedded in the setup directory created by the installer. You can put it anywhere you want. When you run the uninstall routine from the control panel it asks you if you want to repair or remove the program.

>What I would like to see is if I put an EXE on our fileserver and a user clicks on it, Windows could figure out that it is a VFP6 (or VB or VC) exe and then install the runtime and all necessary DLL files needed for the app. And then if any new dlls come along (including VFP6 runtime DLLs), I can tell the app and the next time the user ran the exe it would do the upgrade.

Craig answered this one. Try it, you'll like it!