>Hi George,
>
>>One thing that won't work is changing the title of the Command window to something else and then changing the title of a program window to "Command". I tried to trick it into thinking the edit window was the command, and it didn't work. Sigh!
>
>Because VFP doesn't use the caption, rather the HWND of the Command Window. The window is created upon startup, and even if you close it, it's just made invisible. It doesn't respond to WM_DESTROY, WM_QUIT or WM_CLOSE. You can close the client window inside the Command Window, though. Then the output of the option dialog is displayed in Sans Serif right into the Command Window, but doesn't persist, of course.
>
>I suppose you can search memory for the Command Window handle and change it, should make your edit window behave like a Command Window. *g*
>
Christof,

Are you sure that, internally, VFP isn't using its whandle rather than hWnd? It doesn't surprise me, due to the way VFP handles system messages, that the Command window doesn't respond. Indeed, in doing some tests, I found that simply sending a WM_CLOSE message to a VFP child window resulted in, not only the window closing, but VFP as well.