>Terry,
>
>I don't think I have anywhere in my app a PRG class based on an OCX class (if that is what you mean). I do use a couple of OCX classes (DBI Tech) and I simply added the .OCX files to the ISE project. And it works.
>Have you tried simply adding the OCX files to the project? What type of problem do you have with them?

I am using MS OCX VFP8 and InstallShield Express. I am including the "Common Controls' MSM with install shield. I add the ocx, like ImageList, to the forms in a procedure:

*Old Way - pre XP - VFP 7
procedure addimagelist(oform)
oform.addobject('myImageList','ocxImageList','MSComctlLib.ImageListCtrl.2')
with oform.myImageList
*/.... images ..../*
endwith
endproc 

define ocxImageList as olecontrol
enddefine

*New Way - XP - VFP 8
PROCEDURE AddImageList(oform)
oform.addobject('myImageList','ocxImageList')
with oform.myImageList
*/.... images ..../
endwith
endproc 

define class ocxImageList as olecontrol
oleclass = 'MSComctlLib.ImageListCtrl.2'
enddefine

The New Way is supposed to work. The difference is that the oleclass has to be assigned in the DEFINE, rather than the addObject. The old way does not raise the "insert Object" dialog on the design system, but after an ISE install on a clean system a 0x80040112 message pops up about an unregistered activex. The new way pops an "Insert Object" dialog on both the design and clean system

A KB discussed how to do it with newobject. But the KB used a PRG form and class. The KB and help system say as long as DEFINE CLASS is used for the parent class it should work. But I cannot get it to fire with new object on a visual form with a PRG class:
oform.newobject('myImageList','ocxImageList')

But, the information seems to say that addobject, providing the oleclass in inside the DEFINE, should work. My eyes are crossed from google. One guy, bless him, punched a similar question onto every technical blog on the NET - and got no responses. It thought is was a merge issue. So I tried with all the common control merges with no difference.

I did notice one thing. When I tested with a VCX and an imagelist visually dropped on a form - it worked. My exe lost about 80KB in size (just for one object), and for the first time in a long time, I could erase the VFP EXE (after I ran it) while in the IDE (command window) without closing down foxpro.

I wish I could read Russian - there are a lot of posts on this issue at the 'dot' ru blogs. What to do - what to do ...