Then there is the better choice, IMHO, of using DEBUGOUT < message > which outputs your message to the debugger's Output window. In your control baseclass Init method, you could place something like DEBUGOUT program() and you will get a sequence of what fires when a form loads, etc.

>Hola,
>
>There's only one problem with using messagebox() for debugging a form: when you click on the box's OK the focus returns to your form and it's activate method fires.
>
>Try using something that doesn't require user intervention. I use _screen.print("and now we're activating")... and so on.
>
>Alex
>
>
>>Hi Ed,
>>
>>Try adding a NOWAIT clause to your WAIT WINDOW statement, or better yet replace it with a MESSAGEBOX() call instead.
>>
>>Worth noting... about 2 years ago I believe it was Mac Ruebel who did an article in FoxPro Advisor about WAIT WINDOW producing unexpected results and occaisionally causing developers problems when used as a debugging tool. Thus my suggestion to replace your WAIT WINDOW with a MESSAGEBOX() instead. HTH