>>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 the debugger, set a breakpoint on MyForm.Deactivate.

Umm.. I don't think she's trying to SEE the deactivate method. I think she's trying to look at other code but the Deactivate method runs when the debugger pops up instead of her seeing the code she needs.

Patricia, if you're trying to AVOID the deactivate code, I think you're out of luck without a work-around. I find myself disabling both the ACTIVATE and the DEACTIVATE code when I have to do extensive debugging for exactly this reason.

Usually I do it with a text file

IF !file('BPALTIEL_001.TXT')
   ... Deactivate code here
ENDIF

And I NEVER use a file with my last name on it at the client's site. That way the code ALWAYS runs there.

HTH
Barbara