That's true :).

>I think we're talking diff. methods to achieve the same goal :-D
>
>>No, next form knows what function should be available and its activate code will do this job. When you use LostFocus event, you don't know by sure (unless you hard-coded it somehow) what form will acquire the focus next, so rely on next form code, not on this one.
>>
>>>You still need LostFocus then for the system to shutdown certain toolbar/menu functions when the last form is closed :-)
>>>
>>>
>>>>It's not necessarily if every form supports this behaviour. When you leave a form you will fire next form Activate code, i.e. it does not matter what form lost the focus, it matters what form has focus now. It's another story that each form may reset some properties of mediator object to prepare situation which will be analyzed upon next form activation.
>>>>
>>>>>Yes it could but you have more flexibility using the Got/LostFocus as you can test the state of the toolbar or menu selectively according to which form has focus.
>>>>>
>>>>>>Actually, all this code can be put into FormClass.Activate event, i.e. each Form object knows what to do with toolbar, menu and all mediator object properties.
>>>>>>
>>>>>>>Hi Vinod ---
>>>>>>>
>>>>>>>The way I have done this in the past is to put code enabling/disabling toolbars and menu items in the GotFocus and LostFocus of my form classes....this works well because as you move from form to form the menu and/or toolbar may blink but they stay enabled. If you close the last form then they get disabled as there is no GotFocus enabling them again.
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>The only thing is that menu should only become active when that toolbar is visible & that toolbar is visible only when user chooses any form(s) for data entry...
>>>>>>>>
>>>>>>>>Can u pls advs.. How I can do this ??
>>>>>>>>
>>>>>>>>TIA