>>Ok guys ... I know you're not ignoring me. :-) But I posted this question a couple days ago and have gotten zero responses. Since I'm sure
someone out there has either seen this or sees what I'm missing, I'm posting it again to cajole you all into uncovering the mystery for me:
>>
>>I have instantiated menus in top-level forms often w/o problems. But recently in a top-level I'm having a problem with the infamous "This menu can only be called from a Top-Level Form ..." error. The form
is a top-level, of course.
>>
>>When running in development, I can run the application and the menu will instantiate properly. If I then close the application and re-run it I get the error. I have noted that issuing a CLEAR PROGRAM before re-running the application "fixes" it.
>>
>>The menu is being instantiated in the form Init with the following code:
>>
>>
lcMyMenu = ''
>>DO Main.mpr WITH THISFORM, lcMyMenu
>>WITH oApp
>> .MenuName = lcMyMenu
>> .ConfigureMenu()
>>ENDWITH
>>SET SYSMENU OFF
>>SET SYSMENU AUTOMATIC
>>
>>
>>The menu and "Edit" popup are being released in the form Destroy with the following code:
>>
>>
RELEASE POPUPS Edit EXTENDED
>>RELEASE MENUS (oApp.MenuName) EXTENDED
>>
>
>I use TLs a lot, but you're doing something I haven't done here with the SYSMENU involvement. First thought, though probably you've checked, have you NULLified the oApp prop? Also, I use a form prop for the second WITH param (I forget why, there was some problem, I think, a long while ago).
Well, tried your suggestions and no go. NULLed the oApp property, still errs, used a form prop instead of oApp, still errs, tried removing the SET SYSMENU OFF and SET SYSMENU AUTOMATIC statements in the form Init, still errs, even tried removing the code that sets up the menu Edit functions, still errs. The key seems to be that if I issue CLEAR PROG, it then runs ok, but I don't know what it's changing. I must be missing something ... but I'm stumped. Any other thoughts? :-)
William A. Caton III
Software Engineer
MAXIMUS
Atlanta, Ga.