>1) Although this is what I've been practising, I still don't know the reason for making the external name and property name consistently the same. Note that, even if I am doing this, I still receives the error msg.

The external name serves as the object name while the property name serves as the window name. If they're not identical, object will not be found. Declare the public variables at the top most program of your application, just before calling any form to avoid the error.

>
>2) a) If I already have issued:
> DO FORM MyFormName Name MyFormName
> then, why callout:
> MyFormName.Activate()

Actually that's just an example of what I want to do with the form. If the property name is not identical with the external name - say MYFORMNAME2 will be the property name - MyFormName2.Refresh would be my command to refresh the form.

> b) since my external name and property name are already the same, would this be just a redundancy?

If the form's external name is MYFORM and the property name is FORM1 and then your command is only DO FORM MYFORM, you can not issue FORM1.REFRESH outside the form. It gives you an error. Whereas, if you DO FORM MYFORM NAME anyformname, you could issue: ANYFORMNAME.REFRESH outside the form.

>3) If I'll use option 3, how am I going to know the index for the form that I intend to use?
>
>I am testing these commands (do you think their OK?):
>
>IF TYPE('_SCREEN.ACTIVEFORM') = 'O' AND PEMSTATUS(_SCREEN.ActivForm, 'CloseEvent',4)
>_SCREEN.ActiveForm.CloseEvent()
>ENDIF

Unfortunately, I haven't used this approach yet. Try it, who knows it might work for you.

>Another thing, If I make the child form's WindowType = 1-Modal, it seemed to work but the problem is I don't want the child to be modal. I sure wish MS could be more detailed with how they describe their VFP objects!

It's intermittent, sometimes it works sometimes it's not. So it's not sure if that causes the error.