Guys:
I understand that this is not problem for installed executables.

If you open an .scx that contains msacal70.ocx control as follows:

Use test.scx
browse
dbl-click on ole2 field
contains: OLEObject = C:\WINNT\SYSTEM32\MSACAL70.OCX && I added on my system

from my Windows ME, beta system: OLEObject = C:\WINDOWS\SYSTEM\MSACAL70.OCX

My point is that if I use Tool|Options|Controls tab to add an ActiveX control to my ActiveX controls toolbar, drop that control on a form that will be used by other developers in the group (Win95), when they try to modify the form, they will get an "Ole Error xxxxxx, Element not found, ignoring, blah, blah". The Ole control will not be on the form. They go and add it from their system, save to VSS and the next time I need it, I get hosed.

I thought about copying the ocx file to c:\Windows\System, which would solve this problem (I think), but any other ActiveX controls that I "check" in the Controls listbox will get put on the toolbar reference C:\WINNT\SYSTEM32\xxxxxxx.xxx. If this were one of our sub-classes for a VFP baseclass, the internal reference in the class field is ..\classes\mvcontrol.vcx. All developers hd are organized the same so this is not a problem. (My NT 4.0 system has the folders on a D: drive instead of C:) I never dealt with this problem on the NT, but if I had time, I probably, could duplicate it.

I'm leaving in an hour for a week of fishing, reading, EATING, etc. in the peaceful Upper Peninsula, so I'll catch up with all of the replies on the 24th.