>>>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?


The cost is only $245...(InstallShield Express) and it is a good investment. You can install all other apps as well with it and it gives you a very professional appearance.

OTOH, the VFP runtime files are not 'that' large as to clutter up a computer. No more than any other application. I would just leave them there and not worry with it.

Wayne