Well....but in theory object 1 shouldn't even *query* object 2's property directly at all, although it could call an object2.GetProperty("propertyname")...so...essentially...Access and Assign are N/A in a true object environment because you should be using Set and Get style constructs to message between objects....see?


>I wouldn't think so. If anything it supports it. Instead of object 1 setting object 2's property directly, it's set via the ASSIGN method. The only difference is that it's sort of transparent in code. Instead of explictly making a method call passing the value as a parameter, you just assign the value as usual and the ASSIGN method handles it.
>
>My 2 cents. Keep the change!
>
>SNIP
>
>>So....are we reversing central tenets of COM and OOP by using Access and Assign to intercept property calls/puts when there shouldn't be any direct manipulation at all?