Hi Jim,

>This would require that there be a method of tracking methods and properties forward and backward in the class hierarchy. I'm afraid of the performance cost of that alone.

Not at all. When the Class Designer opens a class it reads all the parent classes into memory. After that it knows which method has been defined on which level. When the Class Designer now finds a line in the method code that starts with "PROCEDURE xxxx" and "xxxx" is not in any of the RESERVED3 fields, it can just add it to this field. There's no performance overhead involved in this. Actually, VFP does this: when it finds the method in the parent class, it removes it from RESERVED3 in the child class. I'm really not asking for more than just adding "*xxxx" to this memo field.

Christof