Thanks, Ed.
I'm not sure I exactly understand everything you refer to, but I will try creating an object, create a new property called "myform", and then initialize the name of the form in the "myform" property, and then use your LINKED syntax (as shown in your message).
I'll let you know what happens.


>Tom,
>Regardless to 2.x stuff, it might give you some ideas about modeless forms flashing when started from menu options. It happens because they get linked to local variable, and when meny procedure is over, the variable gets otu of scope and form dies. The safer way is to start forms linking them to properties of some external objects, oApp in simplified case, e.g. if you start a form
>DO Form myform NAME oApp.myform LINKED
>it should not flash. Try it and see how it goes, again I can't speak by sure about mixed of 2.x and VFP situations.
>

>>Thank you, Calvin.
>>
>> I have spent today trying all possible combinations of switching forms to modeless when hiding them, and back to modal when showing them, and can't seem to find the right combination.
>>
>> The best combination for the purposes of standalone use is to have them all modeless. Then, the READ EVENTS works just great. But, as soon as I start up the 2.6 menu, the READ EVENTS just has no effect whatsoever. (Also, I have now Generated the 2.6 MPR menu from Visual 5.0). And that has no effect either.
>>
>> So, bottom line: When everything is modeless and running as a stand alone app, it is beautiful and slick (you would be proud). But, when I fire it from the menu (which has a READ EVENTS), it just flashes right by, as if I had no READ EVENTS at all. And, if I remove the second READ EVENTS, (hoping that the first one will do what it should, it flashes just the same). But, all of the other menu selections and 2.6 screens (unconverted) work just fine.
>>
>> ONLY THE NEW VFP APP WILL NOT WORK from the menu. But it works fine when running by itself. Any help, or ideas from anyone? Nothing covers this type of situation in any manual.
>>