>>>I did use Spy++ and when a user presses F1 or uses the Help menu option, no WM_HELP message is sent to VFP or any other window that I can find. F1 causes a WM_ACTIVATEAPP message to be sent that initiates the help.
>>
>>How were you tracking this? I was checking the process and there was definitely WM_HELP messages went to VFP either in VFP by iteself or a call from VFP to MessageboxEx(). I used the value returned by the MainhWnd() function in Foxtools. I think that the problem with MessageBoxEx() is that VFP doesn't know how to deal with the accompanying structure.
>
>I was tracking this using VFP only. It was my thinking that it really doesn't matter what something sends to VFP, if VFP doesn't have that message in its WinProc, it will disregard it. So I wanted to see what was going on internal to VFP first and then look into the other things.
>
>Yes, MessageboxEx sends a WM_HELP message but VFP doesn't process those to bring up its help. It uses a completely different message. Even using the messagebox that VFP displays when you get an error, if you click on the Help button, a WM_HELP message is not sent. Whatever it is, it knows to send the correct message (WM_ACTIVATEAPP ??) to VFP for Help.

WM_HELP, is sent if ON('KEY', 'F1') = 'HELP'. If it's own error dialogs, then VFP wouldn't necessarily be using WM_HELP. I can't find what message VFP sends to activate it's help, but pressing F1 does generate a WM_HELP message that VFP processes if no dialog is present.