>>>>
>>If you have a sub-class that modifies a property from the default value of the baseclass, and then later that property is removed from the baseclass, that property no longer exists in the sub-class. You don't get any error or any indication that the property no longer exists in the base class, until you try to reference it in code for your sub-class. I would have thought that the sub-class property would have just become a new property belonging only to the sub-class. Is this correct functionality?
>>
>>Heard anything new from Steven Wright lately? :)
>
>
>This behavior is by design, because a parent class knows nothing about subclasses, and subclasses simply inherit properties. So if a parentclass has a property that is removed, then the next time you open the subclass, the subclass simply inherits the parentclass, which won't have that property anymore. Your code may still have references, but code is never checked by VFP.
>


I'm not sure I see the difference between changing the default value of an existing property and adding a new property with it's own value. They both show up in the VCX in the Properties field. How does it distinguish between the two?


>Steven Wright has been quite lately, and I'd really like to see him do a new HBO special. One of my favorite lines is: "You know that feeling you get when you lean back in a chair and almost fall, but catch yourself at the last second? I feel like that all the time." - Steven Wright

How about:
"I was born by cesarean section. Now, everytime I leave a room, I go out through the window." -- Steven Wright