>>Wait windows don't get focus, and don't cause activate/deactivate to fire. MESSAGEBOX(), yes, WAIT WINDOW, no.
>
>OK, I remember what I was doing, something bone headed where the WAITs were messing up the event order and when I changed it to DEBUGOUT it worked fine. I guess it was just one scenario though.
>
>Anyway, a wait state also may cause code to work differently, where DEBUGOUT would show it like it is.

To be fair, a WAIT WINDOW doesn't cause a wait state in the true sense. Yes, it can recive user input, but like with MESSAGEBOX(), the user is not free to cause any other event to fire, she can only close the WAIT WINDOW with a click or a keypress, so the WAIT WINDOW cannot change the event firing order.

I'm not sure what scenario you observed this in, but if you can remember it, I would interested to hear, because I have never had a WAIT WINDOW screw with code sequence.