>Thanks Ed,
>
>So what you are essentially saying is that VFP (whatever version) "looks in the registry somehow for whatever OCX it thinks is supposed to be actually used, disregarding what the refrence in the VCX actually says" Does that sum, it up more or less? please correct me if that is wrong and THANKS! for your help.
>

It's not VFP that's at fault. ActiveX controls (in fact, all OLE Automation objects) are brought into existance by their ProgID. This is resolved by a registry reference. If the ProgID of -any- ActiveX control is changed to point to a different one, whether in a different place or with a different name, the most recently registered control 'owns' that version-independent ProgID.

The registry is a database, part of which is used to resolve ActiveX references in a consistent fashion based on the ProgID. If your name were the basis for identifying you, and someone else came in and 'took over' that name, I wouldn't be able to find you, either, even though both of you live at physically different locations; the unique key can only point at one of you at a time.

>Ken
>
>>This one's easy - they both are referenced by the same ProgID, which is the basis used to instantiate the object. When the ProgID changed in the registry to point to the new control, anything that used to talk to the old control is now redirected to the new one, and it simply isn''t the same thing. You have two choices; re-register the old control and force the VFP6 app to use the old control, or update the VFP5 app form to use the new control.