Neil,
>
>The message handling in VFP is pretty much standard, it gets freaky when it needs to deal with its child windows. I knocked together a FLL that monitors the windows message queue for VFP and the MessageBoxEx behaviour is standard and works. I think the problem lies in the assigning of the HWND in the MessageBoxEx() API function.

That's what I meant when I said that VFP's message handling was non-standard. I wasn't as specific as perhaps I should have been.

I don't think, however, that the problem is the window handle. I used the value returned by the MainhWnd() function in Foxtools. I called the MessageBoxEx() function, using that value as a parameter. I then brought up Spy++, selected the FoxPro process, and monitored only the WM_HELP message. When I either pressed the Help button or F1, the process received the message exactly as it should. It simply didn't process it.

As a result, I don't think that the question is whether or not it receives the message. I think we've both pretty much verified that it does. Rather, I think the question would be, "Why doesn't it react to the message?" In this area, I can only hazard a guess. Giving it some thought, my first reaction is that it's because the FoxPro window is neither the active window nor is it the one that currently has the keyboard focus, it's simply ignoring it. Beyond this, I have no idea. Do you?