Ramesh,

I believe you are in a state commonly referred to as "DLL H*LL".
Try the following:

Close VB, and all applications that use your OCX.

Do a Start Menu>Search(or Find in NT/95)>For Files or Folders
In the Search For... text box type in the name of your OCX (OCXName.OCX),
and click Search Now.

Leave the results open, and open a dos prompt.
For each result:
  Go to the results dir in the dos prompt (cd PathName)
  Type regsvr32 /u OCXName.OCX
Next

Exit the dos prompt, and close your search.

(Note: Follow these directions EVEN if you have a VB Project Group already
built)
No go back to VB.
Open your main code's project.
File>Add Project
Add your OCX project
Click on your main code project in the Project Explorer, and select
Project>References...
You will notice that the project references the OCX, but it says missing
next to it.
Dis-select your OCX.
Close the References dialogbox.
Go back to Project>References...
Find your OCX, and select it.
Close the References dialogbox.
Try running in debugger now.

I hope this works for you. YES IT IS A PAIN!!! :)


John Lick
Sr. Software Developer
JohnRLick@h...




----- Original Message -----
From: "Ramesh Sridharan" <mr_sriramesh@y...>
To: "professional vb" <pro_vb@p...>
Sent: Thursday, March 28, 2002 3:13 PM
Subject: [pro_vb] Re: How to Debug a OCX


> Hi john,
>
>   What you said is perfectly right? Now i can compile
> and run the source code parallely, but still in debug
> mode, The main source code just passes the ocx command
> without going into the source code of ocx. Did i made
> anything wrong?
>
> =====
> Sincerely,
> Ramesh S
>
> ***********************************************************
> *    Do we have atleast handful of inventions which we    *
> *          didn't used (so far) for destruction?          *
***********************************************************
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Movies - coverage of the 74th Academy Awards®
> http://movies.yahoo.com/
>
>