I was thinking they were handling that through smarter versioning. Doing it the way you mention would seemingly leave the same DLL spread out all over the drive. But regardless of that, I'm still unable to put it in the right folder, without manually copying it, and therefore my EXE does not find it and does not run. I think there's a switch that will tell the EXE where to find the runtime (can't remember - never used it before), but that's not a desireable solution for me, either. I never had to think about this in the previous version of InstallShield that shipped with VFP 8. But now, even though I've changed the default location for some of these files, it still places them in the program folder. So now it seems to be ignoring a configuration setting. I'm hoping someone can shed some light on this.

Thanks for your reply.


>>Since starting to use InstallShield 5 Express that ships with VFP 9, I've noticed that the VFP runtimes are not placed in the system folder and are instead placed in the "program" folder (whatever that happens to be for a particular project). The merge modules are set to be installed in the default location for the merge module, which I assume would be the system folder (more specifically, system32), so I'm not sure why they are not ending up there. I can change the setting, I guess, but there are a number of them to change and I was wanting to avoid that and also I was wondering if there was a way to set a global setting. Also, why would this change? Anyone had this problem?
>>
>>Thanks,
>>
>>Russell Campbell
>
>Current Windows preferred is not to install anything in the system folder anymore. (trying to cut down on DLL Hell, I suppose)