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

>>Today I discovered a potential problem between the platforms. We use msacal70.ocx calendar control. On my Win2000 computer it is located at c:\winnt\system32, but on the other 4 developers computers (Win95) it is at c:\windows\system
>>
>>This control is used in one our reusable forms that is always used when the user clicks on the lookup button next to a date field. Is there any solution, other than all of us developing on the same family platform?
>>
>>Using VFP SP4
>>
>>Thanks,
>Mike,
>
>Shouldn't be a problem. There control has to be registered in the registry. That's used to resolved the installed location.