>>It did as you suggested and it gets to the code allright, but in the debugger the red dots are not visible, so I guess it passe right by them.
>
>Yes, I have also sometimes found the breakpoint feature to be unreliable. (Note, however, that I still use VFP 6.)
>
>Then, to the next step (sigh): I found it to be usually more reliable to set a breakpoint on the function / method name. Just open the breakpoint window, and type the name of the method (e.g., "Click").

This has been broken in VFP7. Hopefully they will fix this soon. The only way you can do this kind of breakpoint is to enter: "Click,1", but that only works if line one of your code is executable. If it's a comment, no stop.

>
>Then, you can still set a breakpoint in the trace window, by double-clicking (?) with the mouse.
>
>This is problematic, however, for events which occur frequently, like "GotFocus".
>
>Another, very reliable, method, is to type "SET STEP ON" directly in your code.
>
>HTH, Hilmar.