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).
>
>>That's neat. It never occured to me to pass an object. I wonder if I can pass a map point... Hmmmm... Off to experiment. :)
>>
>>-Michelle
>>
>>
>>>Hi, Michelle.
>>>
>>>My right-click calls my function that defines my menu. Notice that I pass the form object to it < s >:
>>>
>>>

>>>FUNCTION popuprightclick
>>>LPARAMETER l_readonly, o_this, o_form, c_dbc
>>>

>>>
>>>>>You could use _SCREEN.ActiveForm, this point to the current activeform.
>>>>I don't have a framework. I'll try the first option.