Run Time issue

[tk7834]

I've created a .vbg with 2 .vbp's. I set a few breakpoints, and when running the code from VB, it does break at those points. My problem is I am unable to control anything in VB after it hits a breakpoint. I cannot hover over a variable to see a value or move my forms/classes/etc. windows around. All I can do is hit F8 or F5 to step through the code, but I can't even see it step through unless the code it's stepping through happens to be the top window. Does that make sense? That's about the best I could explain it. Is there a setting or something I need to change? I got a new PC and I never had this problem before. Thanks.....

 

[koala15]

A suggestion to see if it is the app or the VB6 installation: can you create a simple "Hello World" app with a variable or two and put in a breakpoint and then see if you can see the variable's value by hovering.

"Life is full of learning, and then there is wisdom"

 

[tk7834]

Hello World app works fine like I would assume it should. thanks.

 

[zemp]

Check the references in your main .vbp. Make sure it is referencing the other .vbp and not the .exe created by the other .vbp.

zemp

 

[zemp]

Could be a .dll file as well. Depending on the second .vbp.

zemp

 

[koala15]

I also thought so, but one must eliminate the obvious.

What happens when you add a breakpoint very early in the code cycle for example: in the first few lines of Form_Load in the "start_up" form and then if that is OK, then move into the code in a logical manner.

"Life is full of learning, and then there is wisdom"

 

[koala15]

Just a thought after reading Zemp's suggestion - what happens when you do a full compile (Ctrl-F5) on both projects withing the IDE?

"Life is full of learning, and then there is wisdom"

 

[zemp]

Often the reference get changed from the .vbp to the .dll. Why, I don't know.

zemp