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?
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
