>>>My database will be installed on someone's network drive, with just the runtime files on local drives. I am trying to figure out the cleanest way for the users to put runtimes on other workstations. I made an install that installed only one readme.txt in a folder called \dummy. It installed some other files, including a setup manager that I suppose is used for un-installing, among other things. I want them to be able to un-install the runtimes in the future. I also want them to be able to delete the unnecessary text file and avoid cluttering their hard (or network) drives as much as possible. Should I make the default folder their windows folder? Then they won't have an extraneous folder, at least. Is there a better way?
>>
>>InstallShield gives you this capability.
>>
>>
>>Wayne
>
>That's nice to know. I'm sure my employer won't want to spend the money, however. Given that I'm probably stuck with the vfp install wizard, what is the best option?

I'd advise that you keep the runtimes installing to a separate directory and keep the Setup subdirectory in place; it'll make life much easier in the long run. I posted a way to hack the Setup Wizard .STF file to not put most of the setup-related files on the target system in the UT FAQ a couple of weeks ago; as long as you follow the instructions and keep the original Setup Wizard install around, you can use the original Setup Wizard package to uninstall the runtime (you absolutely, positively have to keep the SETUP.STF file created in the Setup subfolder on the workstation to uninstall, since that's used to record what went on during the install so that it can be backed out properly. This is another reason to keep at least the runtime files locally on each system; each subsequent install to the common directory would be confused by the previous stations' SETUP.STF file, and the first uninstall would delete the runtime in the common folder, breaking things badly on all the other stations that had installed to that directory.)