>>>>>>I also tried that! no luck... It seems to only work from the form1's valid on the first field. Driving me crazy :{!
>>>>>
>>>>>I think Daniel's right, something is running later...you can try running through debugger to determine what...also, possibly you're doing something that dis-orders the usual firing sequence, I've done that myself :)
>>>>
>>>>I have put the code
>>>> IF WEXIST("frmBuchhilfe")
>>>> _Screen.frmBuchhilfe.Show()
>>>> ENDIF
>>>>in the form1 activate but get an error on the _screen line. frmBuchhilfe is the form.name of form3 which is really buchhilf.scx. It recognizes that the form exists but I don't have the correct syntax to show it apparantly.
>>>>
>>>>Unfortunately, this system is huge and I inherited it for a few weeks to solve some bugs, do some updates, etc so tracing things is very time-consuming!
>>>>
>>>>Help again?
>>>>
>>>>Sally
>>>
>>>What's the error message, then?
>>
>>Unknown member frmBuchhilfe. I get the same error if I use _screen.buchhilf.show().
>
>Yes, I remember having the exact same problem few weeks ago. I worked my way around it by using CREATEOBJECT() instead of DO FORM in calling the next form. By the way, it is form.name you should use in the syntax, not .scx name.
>If you want, you can do it like that yourself.

>PUBLIC poForm
>* DO FORM... Commented
>poForm = CREATEOBJECT(yourForm, < maybe some parameters, if you have them > )
>poForm.Show(1)  %% Modal or
>poForm.Show(2)  %% Modeless
>
>RELEASE poForm

Daniel, if you link form object to some variable and then release this variable then you effectively kill the form, i.e. above example will not work for modeless form. Actually, any newly created form obvject should be linked to some property of higher-level object and this hogher-level object will provide on-request reference to any form in application.