Very interesting. I would consider that a bug, however a minor one.


>>Just curious: if instead of returning .t. or .f. from the method you change a form's property to .t. or .f. and then in the calling function upon return from the function you check the form's value instead, does it recognize that change correctly?<
>
>Oddly enough, the answer is no. I did the following:
>

>THISFORM.TRacytestproperty = .T.
>RETURN .T.
>

>and they both returned .T. as they should.
>
>I then changed them to:
>

>THISFORM.TRacytestproperty = .F.
>RETURN .F.
>

>and they both still returned .T. - which is incorrect.
>
>However, if I had done this instead:
>

>WAIT WINDOW nowait
>THISFORM.TRacytestproperty = .F.
>RETURN .F.
>

>they both would returned .F. - which is correct. Just adding the extra WAIT WINDOW nowait line, or some other change then causes the form to be compiled and reflect the changes.
>
>To take it a step further... I tried the following:
>

>THISFORM.TRacytestproperty = 1
>RETURN .T.
>

>and the changes were made. I then changed the test property to 2,3,4,5,6,7,8, and 9 - and the changes were not reflected. However, when the following was entered:
>

>THISFORM.TRacytestproperty = 90
>RETURN .T.
>

>The changes were made finally - after I added the extra digit to the 9 (which made 90). It just appears that it is not always compiling when a 1 digit change is being made.
>
>I tested a FORM COMPILE per Hilmar suggestions, and the changes are reflected immediately.
>
>Mel Cummings