Hi,

I have a COM exe written in VC++. This exe calls and loads a COM dll written in VC++. This dll calls and loads a ocx written in VB 6.0. The COM dll merely uses CreateControlEx () method to create the ocx.

Everything so far is good and smooth. The whole application workd fine.

My problem is I cannot step thru the VB ocx code to debug. I selected the option "wait for components to be created" in the project properties of VB ocx . I opened the COM dll (VC) code and VB 6.0 code side by side . I put some break points in both the projects. I am smoothly able to step through the COM dll VC code. I expect that as soon as I reach into the CreateControlEx method of the VC code, I should step into the VB code in the usercontrol_initialize() event .

But this does not happen. The createControlEx returns an error saying class not registered.

Now I manually registered the ocx several times....but I still get the same error.

And this problem is only during debug step through. If I run the exe directly everything is fine.
The only was I am able to debug my ocx currently is by putting msgboxes/ logs in the code and inspecting the log file regularly to see the values of the variables changing.

I would appreciate if someone can tell me a way by which I am able to step into my VB ocx code.

Thanks,