Hi Sergey,

The problem for me is that I haven't done much coding of menus, always using the Menu Builder and resultant code. In this case, it looks mostly hand-coded, and it is very dense (many if-endifs, cases, etc.) so I am having difficulty seeing where the central READ EVENTS command takes place.

My current VFP projects all rely on the READ EVENTS command, and my forms all automatically work under this scenario. Was there another way this was done in the past (which I never learned)?

There is a command

ACTIVATE MENU _MSYSMENU PAD programs


I'm having a strange night now, as even the Windows XP search facility won't find files with the content that I KNOW is there, so I am unable to find any READ EVENTS anywhere in the code even if it exists. Do you know if there is any way other than READ EVENTS to process a menu? I see ON SELECTION. Does it somehow override the accessibility of a form in the focus loop?

I'm not sure any of this is helpful at all, but if you have any ideas I'd sure appreciate it!

Thanks for taking a look!

Andrew

>Hi Andrew,
>
>Menu didn't change much since Fox 2.x days so I'm not sure what 'old Foxpro menu coding' means. Can you elaborate?
>
>>Can anybody tell me how to integrate VFP forms into the old Foxpro menu coding structure?
>>
>>I can "DO formxyz" OK, but it doesn't get focus, even if I make it's WINDOWTYPE=MODAL
>>
>>TIA
>>
>>Andrew