Bruce,

>The problem lies primarily in the AddUIEnabler(), Activate() and Deactivate() methods of cPageFrame. I believe the technique I suggested was a way of taming cPageFrame to do your bidding by overwriting those methods. The main idea is to prevent MM's UIEnabler object from being created on each page in the pageframe, and to stop unwanted calls to RefreshForm(), RefreshToolbar(), etc. that originate in the Activate() and Deactivate() methods.>

First of all, thanks for your help! As you mentioned, you should be able to accomplish this by simply overriding the AddUIEnabler method...however, there is no code in CPageFrame's Activate and Deactivate methods...perhaps this is code that you've added to your copy of the Framework?

I recommend this approach rather than creating a new subclass of VFP's PageFrame class because the new subclass would be missing quite a bit of mojo...i.e. passing errors up the container hierarchy, User security, etc.

>OTOH, If you're brave enough to hack the VCX (back it up first), you can open the VCX or SCX as a table, find the PageFrame record, and replace Class from "cPageFrame" to "cPlainPageFrame" and ClassLoc from "cContrls.vcx" to "cMyNewLib.vcx". Since you modified it outside the visual tools, after closing the table with USE issue COMPILE CLASSLIB cMyNewLib, then try your form.>

Even better, you can use the Mere Mortals VCX Editor to more safely "hack" the vcx...check out the Developer's Guide for details.

Regards,