Is the app hierarchy the same as a framework? I only have a vague idea about either of them, and the vague idea is the same for both of them.

-Michelle


>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
>
>>My logic is that when you right-click on a form, it will be the active form, so just referring to the active form works for me. If the procedure were more complicated and gave the user a chance to make a different form active in the middle of it, I'd be in trouble.
>>
>>To be honest, I know very little about OOP philosophies. I know enough to know what an object is and how to use one, but that's about it.
>>
>>-Michelle
>>
>>>Michelle, the normal way of reference any form is to keep OO application hierarchy, i.e. any form can be referenced from higher level object, up to application object. Passing objects to functions is mostly workaround and may not work nicely for modeless interface (surely, shortcut menu is not exactly modeless).