Hi Sam ---

>
>These new Assign methods are going to get really scary really fast when code get obsured behind an = sign. Imagine debuging a code fragment like "this.that = x" when it crashes the system. Or when this.that = y causes your entire interface to dance around and change colors.
>
>I guess that its going to take sane programmers and great documentation to avoid a mess of problems!

Well...like any other paradigm it can be used or abused, both to great effect. And it won't be that tough to debug...if an Assign or Access bombs, the degubber will be pointing to that method code, not the "this.that = y" portion. I have found, and related in earlier threads with others, that A&A are godsends vis-a-vis centralized state logic when you wish to enable or disable controls based on a flag or other property that tracks a containers "state" --- like Edit, Append, Delete states (John Petersen explores the form "state" concept well in VFP5 Enterprise Development).

And it doesn't take sane programmers nor great documentation. It takes decent programmers who design well up-front and are consistant to their own standards. Basically, try it, you'll like it!