Hmm, very strange.

Did you tried TYPE("m.myform.name") instead? I just thought VFP might thins "myform" is an alias when EXACT=ON.

>"myform" is created with DO FORM ... NAME myform LINKED and myform is public (I was trying both metods); I use this because the form is accessed from another form and is not active at this moment.
>The error appear only on testing if form is opened (with TYPE) and not in folowing code where I use myform.new(), myform. .....
>I use this code from 3 months just fine and error appeared today.
>
>Thanks
>
>
>>Hi!
>>
>>Is "myform" variable created by you explicitly or this is the variable created by DO FORM command for the form? If the second case, DO NOT USE this variable to access the form and its properties. This is because:
>>
>>1. In run-time (in EXE) such variable is NOT created.
>>2. This variable exists only for debugging - when debugging form, you can use this variable to quickly look to the form's properties and objects.
>>
>>Because this, I suspect VFP features for such variable might work werdly or incorrect. I also suspect that these variables have no purpose for programming, so were not tested by MS under such circumstanses, just because no use-cases.
>>
>>To access current form, use _Screen.ActiveForm.
>>
>>If you want to use public variable, create it explicitly in the Load or Init event of the form and release explicitly in the Destroy event of the form.
>>
>>
>>>Hi
>>>
>>>I dont know what to do: the TYPE function return different values according with SET EXACT
>>>
>>>EXACT=ON => TYPE("myform.name") gives "U"
>>>EXACT=OFF => TYPE("myform.name") gives "C"
>>>at both times TYPE("myform") gives "O"
>>>
>>>Doru