>I tried your technique on a pair of sample forms under VFP 5.0a. The good news is that it works fine, the bad news is I was unable to reproduce the behavior you describe. Maybe it would be helpful if you ran a similar test yourself, outside of your app, to see what results you get when the code is isolated from the other stuff that might be happening in the app.
>
>As an aside, I did wonder how you were referencing the pad name you're releasing in the deactivate event, since the pad name in a generated menu program (.mpr) changes each time the menu is compiled. In my test, I took the cheap way out and hard-coded the pad name in the Release command.
>
>>Hi Rick,
>>
>>I'm not PUSHing or POPping the menus and there does not appear to be anything unusual in the generated MPR file. The only reason I suspect the way I'm handling the menu is because when I close the app after extended use (i.e. the forms that call menus this way are launched 40 or 50 times) the menu bar flickers madly as if there were a whole bunch of POP MENUS occurring consecutively. But I'm not using PUSH/POP so I can't explain that behavior.
>>BTW, I'm running VFP 5.0a.

Another thing that may cause a lot of menu activity is the SKIP FOR - it gets reevaluated more often than we think, most probably when a form loses/gains focus. The heavier the reevaluation (i.e. expressions vs functions vs just variables), the longer it takes, and of course, the richer the menu structure, again the longer it takes. Anyone who watched the debugger in ProMatrix had nice (waste of) time with this.