>>When I use the debugger to try and see what's going on, the Deactivate method of my form or page runs before I can see what happened. I've used DEBUGOUT and the debugger's event tracking to circumvent some of this, but that's not good enough. Does anybody have any other strategies for coping with this? I'd like to get control in the debugger BEFORE the Deactivate code runs. TIA for any ideas.
>
>In your code where you want to break, SET STEP ON. This will cause the debugger to pop up at that line of code.
>
>
>HTH
>
>Wayne

IMO, this is not good practice. If you forget to remove the line, the user will get a "Feature not available" error. You are better off setting the break point in the debugger.