Mike,

>In that case, the bottom line is, for another developer using your classes or forms wants to change xProp, he sets it. If the value is totally off, you can give himw a property specific detailed message. Otherwise he would try it, find out the properties hidden, perhaps stumble accross the SetXProp method, than have to learn any syntax.

Hmmm. I'm not sure if this would be a disadvantage. I really dislike the idea that a ASSIGN event could rollback a value without a error message or warning. This could make error tracking a real hell.

What if this property was set at Development in stead of runtime ?? It won't work. If the assign statement would work in development time, I agree, it would help to hide implementation details of objects.


Walter,