Cesar --

Most interesting! I had heard that using MemberData could slow things down, but had not suspected it would be such a big hit when merely doubled the number of inherited items.

Thanks for the warning. I'll not waste time on it in PEM Editor (which, BTW, will have a new and improved version out shortly)

>>All Hail, Cesar!
>>
>>You have any success with this ... that is, with using subclasses that each could get to the limit?
>>
>>(I'm having the same issue in the next release of Edit Property/Method, which will be renamed PEM-Editor, and should be released soon.)
>
>Hey Jim !
>
>Happy new year !
>
>Yes, using subclasses we can expand the Memberdata usage.
>At this moment, the memberData for FoxCharts uses 16K - 8K in a Baseclass and more 8K in the subclass. And it is being used only for the properties that are for users access.
>
>All internal properties are not using MemberData at all.
>And this is making the class usage in design mode to become really very slow.
>
>The truth is that I'm almost giving up completely the MemberData usage.
>
>For your case, I would not use MemberData at all, because the properties are only used internally
>
>Or am I missing something there ?
>
>Cheers
>
>Cesar