Hi David ---

>Assign/Access can be thought of as owner object safety nets. You can prevent your object from being assigned invalid property values, and give them back a result that is potentially filtered. ie they ask for the value of cTopSecretPassword and the object just always replies "None of your business"
>

Oh, I know....and they also enforce the rule of an object changing it's own properties.

>Personally I HATE the thought of writing Get/Set for every darn public property. Sometimes practicallity just has to win out over OO puritism. And as long as it's the declared public interface to an object who the heck really cares if it is:
>
>? oObject.TheProperty or ? oObject.GetTheProperty() or ? oObject.Get( "TheProperty" )
>
>personally I prefer the first.
>

I agree with you 100% in practicality.....Gary also convinced me....I've just been rereading some theory books.