There are often errors that will occur in an application when the debugger is open. Most common (in my experience) is an error on an activeform or activeobject. Since all the usual deactive methods fire in your application when the debugger is activated, sometimes an assumption you've made about what will be defined is...er...erroneous.

I do two things: 1) I've gotten alot better about not making ANY assumptions about context (which, IMHO, ActiveForm and ActiveObject do). 2) I put minimal action code in Activate and Deactivate methods. I know a lot of people put save code and whatnot there, but I just don't really like that. 3) If I know it's just because the debugger is running, I may not care and just choose to ignore it.

If I had to guess, I'd guess that there is a breakpoint or condition in the application that is firing the debugger... Then if you click on the menu (and the debugger is actually active) you *can* (I have) get these "context" errors. First, I'd look at the debugger and at the callstack to trace back to see where the break is really originating.

I know this might be awfully vague, but I hope it helps some.


>I am getting an error that I cannot track down. The error ONLY occurs when the debugger is up. The line of code displayed in the debugger is the "ACTIVATE MENU (m.cMenuName) NOWAIT" from the .MPR. The error is "Unknown member poActionList", which is code from (somewhere) outside of the MPR.
>
>The error comes up in a VFP dialog box with only OK and HELP buttons. It does not matter if I have a custom error-handler, or the default, this error comes up in its own dialog box.
>
>Is there any way to track this down using the debugger?
>
>
>Bob