Again, doesn't passing the object (such a tidy package) to a business object (?) that does something to a form...seems correct. The business object (eek) shouldn't care who happens to "own" the passed object. IOW, if I'm designing for reusability, an object might be added to very differeng hierarchies. Forgive me if I misunderstand.

>Yes, passing single object will help in simple situations, especially when launching something modal (form or menu). The app hierarchy means that you have object links between all objects in your application, i.e. when you create an object you link it to some property of higher-level object. The simplest example is to start forms linking them to app object properties:
>DO FORM myform NAME oApp.myform LINKED