>Is someone experiencing the same bug with the PEMSTATUS function in VFP 5.0a?
>
>In a toolbar a toolbutton determines if it should be enabled or disabled by check if the active form has a particalr method.
>
>The most efficient way is something like this
>
>THIS.Enabled=TYPE("_Screen.Activeform")="O" AND ;
> PEMSTATUS(_Screen.ActiveForm,cMethod,5)
>
>But this code sometimes leads to internal references to the form object thereby preventing the release of the form (e.g. clicking the cross).
>
>By rewriting this code into
>
>lAcces=.F.
>IF TYPE("_Screen.Activeform")="O"
> lAcces=PEMSTATUS(_Screen.ActiveForm,cMethod,5)
>ENDIF
>return lAcces
>
>the problem gets less but does not dissapear entirely
>
>I've already reported this behaviour to Microsoft, but i didn't get a conformation of this BUG (not reported by Technet or Dev studio)
>
>Does this behaviour occur in VFP 6.0 ?? Are there any know 100% workarrounds (besides the AMEMBERS function) ?
>
>
>Thanks !

I've only seen the problem when PEMSTATUS is used on the same line as TYPE('object') or another call to PEMSTATUS. I have been able to get around it by simply breaking up calls like this into separate lines.