"Can't enter break mode at this time" (Issues with adding controls at runtime)

[mc84excel]

Hello All,

I have recently been working on a form which has its buttons added at runtime. It works well except for one problem. Suppose I am debugging one of the procedures that are called from the buttons. I insert a break point in the VBA editor. When the code reaches the breakpoint, VBA displays a message "Can't enter break mode at this time"

This is frustrating and I want to find a way around this (so that breakpoints still work).

I have tried googling the problem - the problem appears to be well known (although most of the discussions revolve around adding controls to a worksheet at runtime) but I can't find any definite solution.

Any help would be appreciated.

[Norie]

Is the code for the buttons also added at runtime?

[mc84excel]

Yes. Form, controls & code for controls are added at runtime.

[Norie]

What code is it you are trying to debug?

[mc84excel]

Any code that is called from the controls added at runtime.

(The content of the called code doesn't matter because, from what I have found by googling, the problem is caused by adding controls at runtime).

[Kyle123]

Are you adding them normally, or with some nasty hacky code that writes code for each button?

[mc84excel]

Are you adding them normally, or with some nasty hacky code that writes code for each button?

What's the difference? (I'm still a novice)

Probably the latter I guess. The adding buttons to a temp form has this "can't enter break mode" issue.

[Norie]

What do you mean by 'temp' form?

If it's temporary form why is it temporary and what's its purpose?

[Kyle123]

I suspect the IDE doesn't like you trying to debug at the same time you're trying to automate it. If you add the controls in the normal way, this issue won't occur as per the other thread

[Izandol]

If your code performs an action that would result in a state loss you may not step through it - that is the same issue with adding controls to worksheets.

[mc84excel]

What do you mean by 'temp' form?

I was using shorthand in my reply to Kyle to refer to another one of my threads here. (One that you and Kyle have both helped me on)
http://www.excelforum.com/excel-prog...t-runtime.html

[mc84excel]

If your code performs an action that would result in a state loss you may not step through it - that is the same issue with adding controls to worksheets.

But I receive this error message on code that doesn't result in a state loss?

[Norie]

What error message?

[mc84excel]

I've found a possible solution http://support.microsoft.com/kb/q155051

But how do I programmatically add a non-ActiveX control to the form instead of an ActiveX control?

[Norie]

As far as I know only ActiveX controls can be added to userforms.

[Izandol]

But I receive this error message on code that doesn't result in a state loss?

If you would like a complete answer you must frame a complete question: what is the code?

[mc84excel]

As far as I know only ActiveX controls can be added to userforms.

That's what I thought but I was afraid to say so (I'm still a novice)

What on earth does MS mean then? (in the MS Support link)

[Norie]

The causes of the problem are described as,

•You programmatically add an ActiveX control to a worksheet.

-and-

•You step through the macro.

no userform mentioned.

[mc84excel]

If you would like a complete answer you must frame a complete question: what is the code?

Sorry I don't have time at the moment to create generic demo code to recreate this issue.

Otherwise if an existing workbook is fine, see thread http://www.excelforum.com/excel-prog...t-runtime.html and "GoTo" * post #10 and dl the attachment. From memory that has this "can't enter break mode" issue.

* (injoke between me and Izandol)

[mc84excel]

The causes of the problem are described as,

•You programmatically add an ActiveX control to a worksheet.

-and-

•You step through the macro.

no userform mentioned.

Yes I know But the issue described is very similar to what I'm getting. The difference is the cause. I incur the issue when I programatically add ActiveX controls to a UserForm and then run the code with breakpoints set.

[Kyle123]

The difference is the cause.

You've hit the nail on the head there - this isn't the same issue...

Just add your controls properly, stop hacking the IDE and live in bliss

[Izandol]

Your workbook in the previous thread did cause state loss because you were altering the actual VBProject by using the Designer.

[mc84excel]

I'm marking this thread as solved.

Don't add controls to forms at run-time.

If you really need to, there is an alternative method of adding controls (thanks to Kyle123) - See http://www.excelforum.com/excel-prog...t-runtime.html