Originally posted by Megatron
Whoops, my mistake.

Yes, so long as the ActiveX DLL, and the client application are in the same thread, you should be able to subclass fine.

This makes me curious though, how are you implementing a completely new DLL into a pre-compiled executable? (Maybe I'm missing something, here)
Well, here's the deal: We have been asked to write an ActiveX DLL using all the specificiations given for the same, and it's supposed to work with an EXE file. I don't even know if the EXE will be in VB, but commonsense tells me it should be. Anyways, one of the specification requirements was the dynamic menus, which I guessed must appear in the EXE's menubar. That prompted me to think and stumble across these problems.

For the moment they have said they will handle the menus at their end, so I don't know if they are going to build static menus to invoke and manage our DLL or we shall be asked to do it later.

Hope that clears it up. Also I don't think there is any existing DLL. We are writing it up from scratch.

.