>>>>Otherwise i must use cyanide to stop my baby from crying.
>>>
>>>I think what Jim trying to say is that you should have a similar program like this:
>>>

>>>Procedure FormCollect
>>>Lparam cformname
>>>For i = 1 To _Screen.FormCount
>>>   * check if the name of the form is equal to your reference form name
>>>   If Upper(_Screen.forms(i).name) = Upper(cformname)
>>>
>>>      * do whatever you like to do in the form here
>>>      _Screen.forms(i).Activate
>>>      Exit
>>>   Endif
>>>Endfor
>>>

>>>
>>>Call the form anywhere in your application without declaring it public.
>>>

>>>Do FormCollect With 'MyForm'
>>>

>>>
>>>Another way is that Invoke the form specifying the name in the do form command:
>>>

>>>Do Form Myform Name MyformName
>>>

>>>
>>>so that you can call the form by its name anywhere in the application:
>>>
>>>MyFormName.Activate
>>>MyformName.Refresh
>>>
>>>etc.
>>>etc.
>>>
>>>jb
>Ooops.I have send a blank message.
>Procedure Formcollect is good.
>I can use it.
>Also i cant see my form in the debugger too.
>
>Do Form MyForm Name MyFormName
>MyFormName.Show
>generates the same error
>
>You say that i must use public variables.
>Using public variables solves my problem.
>My Jim Booth Says that using public variables is not usefull.
>But i can only see my form in the debugger when i use public variables.

Actually he didn't say it's not useful. Jim is a proponent of not using PUBLIC variables too much. It has something to do maybe on resources being used in your PC.

As for not seeing it in the debugger when it's not declared as public VAR, maybe because it's not treated as a Variable. Let me ask you something, what's your main reason why you should see it in the debugger???

jb