>>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.

If this is stored in the FoxCode table, would it would be specific to a fixed PC; i.e., if the SCX/VCX copied to another PC the capitalization would be lost? If it is stored there (FoxCode), is it also stored with the SCX/VCX in the memberdate property (upto the limit of the 8K)? What was the reason for the 8K limit on the length? I am storing in the user memo field lengths longer and they work...

Greg