George,

So do we call it a bug? - or is there some "explanation" (as far as you know) MS has put out?

Ken

>>Ok,
>>
>>I must not be understanding something here.
>>
>>I have a class with a property - MyProp. I have a MyProp_assign method. I have a public method SetMyProp() that sets MyProp to a value. The idea is that calling SetMyProp() will "go through" MyProp_access for some validation. All this is in one class - no subclasses involved.
>>
>>if MyProp is public or protected - then issuing SetMyProp('value') correclty calls the MyProp_assign() method. However if MyProp is hidden - then SetMyProp does NOT make MyProp_assign fire even though MyProp gets changed correctly. The Public/Proitected/Hidden of the MyProp_assign() method seems to make no difference.
>>
>>I do not understand what is going on here. The MyProp_assign() method SHOULD have access (no pun intended) to MyProp - so why is it not firing? I want MyProp hidden so that future subclasses can not change it directly.
>>
>>Thanks,
>Ken,
>
>I've noticed the same thing. _Assign does not fire if the property is hidden. You're not missing anything here.