>>For .Net I think it's defined in ECMA-335 (as “A class member that defines a named value and the methods that access that value. A property definition defines the accessing contracts on that value. Hence, the property definition specifies which accessing methods exist and their respective method contracts" )
>
>Thanks
>
>>No. But the definition of a property may be looser in other environments. AFAIK in JavaScript, for example, any publicly accessible class data member accessed via the '.' notation is referred to as a property.
>
>Maybe someone can correct me, but I believe we saw the same as well in VFP.

IIRC the VFP behavior was pretty much like a .net automatic property - i.e get/set methods were created which then could be overridden using the xxx_access and xxx_assign methods.