I had considered that approach, but it would mean adding the keypress event code to my base form class, which possibly would not have been executed by some of the 260+ instantiated forms in the system that had local keypress code already--so a massive editing project would ensue. The same issues would apply for the active form's click method.

So I came up with another solution which works well for me: just put a call to the "Wait form's" release method in the MouseEnter event of the contained edit box. So if the user moves the mouse cursor over the wait window form, it goes away. It also has a timer to implement a TIMEOUT type function, so if it's not in the user's way, it goes away on its own after a specified time period. These methods have the added benefit of not triggering the whole LostFocus, Deactivate, Activate, GotFocus fandango in the calling form.

If anyone is interested in my class, I could post it to the downloads section.

>Ok; as I told, original Nigel's utility has some limitations but you could add features as you need. For instance, to release it you may add to form.keypress, form.click and form.deactivate the line:
>
>thisform.release
>
>It is called like /DO FORM mywaitwind NAME frmWait WITH "Text to display"/;
>so to release it in nowait mode you should issue instead of wait clear:
>
>frmWait.release
>
>In the past I modified the utility and add timewait parameter and others:
>
>LPARAMETERS pcMessage, pnTimeWait,pnBorderColor,pnBackColor,;
>pnForeColor,pcTextFontName, pnTextFontSize, pcTextFontStyle,pnFlashType
>
>
>>Thanks for the tip, Yuri. I found another wait window class in the downloads section besides the one you reference and checked them both out. One simply repositions an actual WAIT WINDOW command, so has no color control, while the other relies on a hard-coded programmatic call to the "waitform's" release method to destroy it. So still no solution to mimicking WAIT WINDOW NOWAIT behavior.