Hi Mark ----

>
>So, does how will your UI get a value of an object property?
>

Well, usually just lcCharVal=Obj.CharProperty. Since we have Access and Assign now and since I have been convinced they are proper by some OOP standards (in a thread here not long ago) and since Access methods can control what is passed back to the UI.....no reason not to.

The trick here, of course, is to have Alert behavior at the superclass level for non-visual objects and *plan* for static coupling with those constructs within the application at the instance level.

So....in my app, if I have a business or functional object that is called, I *know* that it will have the Alerts collection and other supporting features just as I know that it'll have Init, Destroy, etc...

Again, this relates to a larger pattern concept I have been working on for a bit and have almost finished writing a paper on. Stay tuned :-)