Now thats interesting. Maybe thats why I couldn't duplicate the problem: I was putting wait window nowait after the parms statement to display the value.

>
>It's a label object as a member of a container object (whose visible property is always .F.). The strange thing is that if there is code after the LPARMETER statement, then it works fine.
>
>Example:
>
>PROCEDURE visible_assign
>LPARAMETERS tlVisible
>
>[Code Segment]
>
>?VARTYPE(tlVisible) *** returns L as expected
>?tlVisible *** returns .T. or .F. as expected
>
>This.Visible = tlVisible *** no problem
>
>ENDPROC
>
>This leads me to woder if there is some sort of wait within the _assign method.
>
>Then again, I'm still using the March pre-release so that may be the problem - guess it's time to cough-up for VS ENT. Thought that if I held out through the new year, the SP release would include SQL Server 7.0.
>
>>Hi Jeff ---
>>
>>I don't see this. What type of object are you trying this with?
>>
>>>
>>>I have noticed that, in some cases, the parameter received by an _assign method is not what was passed - or that there is some sort of wait within the _assign method before the parameter receives the value.
>>>
>>>For example:
>>>
>>>This.Visible = .T. should pass .T. to the tlVisible parameter in the following _assign method, but it doesn't. The changing of the default "vNewVal" to "tlVisible" makes no difference.
>>>
>>>PROCEDURE visible_assign
>>> LPARAMETERS tlVisible
>>>
>>> ?VARTYPE(tlVisible) *** returns N (a numeric)
>>> ?tlVisible *** returns 0
>>>
>>> This.Visible = tlVisible *** returns an error (obvoiusly)
>>>
>>>ENDPROC
>>>
>>>Iv'e also experienced a similar problem with assigning object referrences.
>>>
>>>Has anyone else experienced this?
>>>
>>>TIA