Hi Trick,

Your code looks SUPER cool.

I haven't done much testing. However, if you don't mind, a couple of questions.

  1. First, this stuff runs the ActiveX.dll as in-process, correct? I'm hoping that's the case, as I want to pass my ActiveX.dll an open database and some open recordsets, and have it use them just as the main program would.
  2. Next, my actual ActiveX.dll files will also have .ocx dependencies. I'm assuming I can just embed a .manifest file in each of them to take care of that. Would you agree with that?
  3. I will have the source code to my main project as well as all the ActiveX.dll files I create. Therefore, even though it's late-binding, I will know each class's methods and properties (and I'll use them correctly). Therefore, I'm assuming I can just delete the GetAllCoclasses , CreateIDispatch, ITypeLib_GetTypeInfoCount, ITypeLib_GetTypeInfo, and ITypeInfo_GetDocumentation procedures. In other words, I believe I'll only be calling CreateObjectEx2 (and what it needs) and UnloadLibrary. So, I can delete what those don't need. Is that correct?
  4. Lastly, so ... I need to call UnloadLibrary when I'm done with the ActiveX.dll and I want to get it out of memory? Correct?


Again, Trick, if this all works like I'm hoping it will, this is totally cool stuff.

Thanks millions for sharing this. If all goes as expected, this is going to be huge for my project.

Elroy