>>>>Bud: The behavior of the wait window is much different to a normal form. A Wait window call never fires a deactivate of an active form. Bud a form does.
>>>>So: What do you do?
>
>>How about a generic form? It can set to be a popup with a timer to automatically timeout if needed. It can BINDEVENT() to whatever the focus form is and intercept mouse moves and keystrokes to auto-go-away when it's time. It could then store previous messages to a log, allowing them to be viewed later, reported on, etc.
>
>But that doesn't solve his main problem, that using a form rather than WAIT causes events to fire on the form that's losing focus.
>Tamar

If the OP needs something that won't trigger events or cause a break in program flow I could provide an FLL/DLL that instantiates a window in the parent HWND which simulates the WAIT WINDOW programmatically, but does not interrupt the main VFP event loop or procedural flow.

In code a call would be made to the new thing with the text to render. It could render it with the various WAIT WINDOW parameters, but without causing any break whatsoever in VFP's execution environment.

Could be a handy generic add-on too.