>Hi Cesar.
>
>>Couldn't it update the FoxCode table ? I'm sure the Intellisense's father could find some ways :-) ??? <bg>
>
>Actually, you're sort of right. Member data can go into the FoxCode table, but then it's not specific to a class. However, that's probably not a big problem. You can do that now using the MemberData Editor by choosing the Global setting. Perhaps we could change the New Property/Method and Edit Property/Method dialogs to handle that as well.
>
>Doug


Hi Doug,

That sounds promising.
Anyway, it wont work for a class that I want to distribute.
When a user opens the class, it will still work with the 8K limit.

I've just received a tip from another friend, telling me that I can use the *K limit between subclasses, so I can use a base class, add the PEMs that I need, till I reach the 8K. Then, I can subclass it, and the Memebrdata from the parent will work together with the limit of 8K from the subclass.

I hope to make some tests with this possibility in the next few days. It seems right now that this would be the best workaround for my case.

Thank you all for the replies and valuable suggestions !

Regards

Cesar