Yes it is, or at least something like that. I tried that approach using many message combinations, and via the debugger got to stop on a message. But the "break" did not succeed in exiting the while loop.

Somehow one of the multitude of messages must have restarted it.

I think I will give up this approach and try a modal dialog box or even a thread isolated all by itself as it waits. Will need to have a user option to cancel the wait.

Something dumb is happening that keeps restarting the while loop. I have exited sometimes by including the 'WAIT_FAILED' condition.

Its clear there is too much stuff going on I don't understand. My own diagniostics are probably creating a mass of messages.

The thread approach with a WFMO() function instead of the MWFMO() function appears much safer even though it is a lot more work.

Brian