Larry-

Mike hinted at a solution for you. You can simply subclass your baseclass control and hide whatever PEMs you don't use. (This works for native PEMs, not just custom properties and methods). Keep in mind that hiding, say, the click method can really mess up how a control works. >s>

>Is there any way to reduce the number of properties that are available for a control on a form? Usually there are, maybe six properties that I really need to deal with and the other 167 are superfluous, most of the time. I'm getting carpal tunnel from scrolling through all the properties each time.
>
>Or that that what a VFP Builders do, and I need to subclass my control and make a builder for each one?
>
>Sounds like an enhancment request for Version 7.0.
>
>-- L