The "DO MyMenu.mpr" is called near the beginning of the legacy 2.6 PRG.

The forms behave as described in all details the same whether Debugger is ON or OFF.

This "sharp learning curve" is cutting into my neck.

After "Do MyMenu.mpr" the original legacy FOUNDATION READ (programmed by
my predecessor) is established. After converting to Visual, I replaced the
main READ with READ EVENTS (which works fine for all of the other 107 menu
selections). It is only when the Menu fires up my newly created Visual
application that things creak and croak.

I had added a new menu pad which only calls my new PRG.


>Tom,
>When do you

DO MyMenu.mpr

?
>Do the forms behave correctly when Debugger is off?
>
>Menu functionality has changed little between 2.6 and 5.0.
>Sorry about the frustration, I remember spinning off of the sharp learning curve many times...:)
>
>Mark
>
>>My reference to "logic" was a shorthand way of referring to the PRG where I have the
>> DO FORM2 NOSHOW
>> DO FORM1
>> READ EVENTS
>>
>> When I fire up the PRG (with the above code in it) from the 2.6 menu, the debugger shows that the debug pointer returns to the menu READ EVENTS, and the forms are non-reacting to events (like mouse clicks).
>> (Remember, this happens when the forms are modeless. But, when I go to modal, the forms do react to mouse clicks, etc., but the debugger pointer stops after going from form1.hide to form2.show and back again to form2.hide and form1.show.)
>> So, also remember that as a standalone with modeless, the forms work beautifully (until a clear events is issued, as normal). But, being called from
>>the 2.6 menu seems to confuse things.
>> Thank you very much for your willingness to join this frustration with me.