>Bruce,
>
>I double checked that I could find your explanation on how you accomplished pf on a pf but could not find where I had saved or printed it. Could you send me your response again. I don't seem to be able to retreive the message from UT anymore.
>
>Gary.

Gary,

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.

I actually recommend NOT using the cContrls.vcx cPageFrame class at all, but create another subclass of PageFrame, say cPlainPageFrame in a VCX of your choice. Drop this *new* pageframe onto the target in Class Designer/Form Designer and you're all set.

If you already have lots of work put into a cPageFrame, I recommend doing cut-and-paste surgery. Cut the pageframe and save it off to a "palette" form. Drop an instance of your new cPlainPageFrame class onto the designer, and copy your textboxes and other controls from the "original" to the "new" pageframe.

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.

Hope this helps.