I am working on a project with multiple developers and some of us use NT as our development platform and others use Windows 95/98.

In VFP 6.0, I subclassed a third party ActiveX control [.VCX instead of a code-based subclass] to create some custom properties and methods. It works. All is fine so far.

When any other developers who use Win95/98 try to modify this subclassed control, they get an error message and cannot even open the class from the class library.

We all have appropriate development licenses for the control. The Win95/98 developers can use the [non-subclassed] control and can even create their own subclasses of the base control. They only fail when they try to modify the subclassed control which was created on NT.

We looked into the raw data stored in the .VCX and discovered two memo fields: OLE & OLE2. The OLE2 field contains a hard coded references to the .OCX. For example:

OLEObject = C:\WINNT\system32\CTEXPL~1.OCX

We have tried to change this path to C:\Windows\System on the Win95/98 machines but that still doesn't work.

Anyone have any ideas what else to check?

Guy