>>>>Well, from one of his messages (the one that gives a code sample), it's pretty clear that he created, in fact, an OCX in VB. Which, is the same as an ActiveX DLL.
>>>
>>>ActiveX DLL's are not OCX's. There is a difference between the two.
>>>
>>>ActiveX Controls (which are files with that have an OCX extension) consist of everything that the DLLs have except they cannot expose public objects other than the control itself, and they support multithreading. Also, must be sited on a container. Also, they have the built in know-how for property pages, and interacting with a property browser. The can only be in-process.
>>>
>>>Some of this information was taken from Daniel Appleman's book called, "Developing ActiveX Components with Visual Basic 5.0"
>>>
>>>I think I'm close, but I'm still having some trouble with my Define Class. I think that I just need to create a class based on custom, add my object, and then code for the varying events. But, I can't quite get the right combination yet.
>>
>>And what is an ActiveX DLL?
>>
>>Vlad
>
>An ActiveX DLL is a COM object that is In-Process (can be out of process, and then would have an EXE extension), is not placed on a container, should have no visual elements, can be instantiated and released with code.... and I am missing out some other things.

Thanks. I think I got it. So, you're ActiveX DLL is an object after all. Only that is not visible.

BTW, an .ocx file can be an ActiveX DLL. You can create such OCXs in VC++.

Take a look to OleControl in VFP's Help file. Click on the Example link. I think it gives you a sample code that is almost exactly what you want. Just change the Excel object with your own. It should work.

Vlad