>Hi George,
>
>As a related issue, what happens if the normal practice of a developer is to install the VFP runtime .DLLs in the application directory (or even third party ActiveX controls), and then two different applications following this practice are installed on a single customers PC?
>
>i.e., C:\VFPApp1\VFP6Run.DLL and c:\VFPApp1\SomeActiveX.OCX
>then later, C:\VFPApp2\VFP6Run.DLL and c:\VFPApp2\SomeActiveX.OCX
>
>Does this create some sort of conflict in the registry? Wouldn't the act of installing/registering the second application overwrite the entries of the first application?
>
>I've wondered about this especially since in Windows 2000 you aren't supposed to be putting your own .DLLs, etc in the System directory.
>
Guy,

Admittedly, and principally because I don't have a machine using I'm not completely up-to-date on how Win2K would handle such a scenario. Obviously, since stuff isn't supposed to go in the system, there has to be some sort of mechanism implemented to keep this information straight. How it's implemented, I'm not currently aware (but you can bet I will be in the near future< g >).

In previous versions of Windows, dumping stuff in the system directory was the road leading to DLL Hell. In fact, if you check my "Lotus Position" post, that was a problem there...getting the versioning problems worked out. The same applies to ActiveX controls. One ActiveX control (or automation server, etc.) overwrites another, and "Bingo!", versioning problems. However, using the system directory in this case does solve the registry entry problem.