>>I think that these methods fail because of a simple hard fact: there is no
>>built in automatic mechanism that watches the values of properties of
>>controls and notifies us. Each property takes care of itself internally,
>>and the people who designed those controls didn't think that we developers
>>need to automatically know when the value changes. If we want to know, we
>>have to check it ourselves. The timer method is not only (I believe) the
>>best method we have, but it is the published and standard method not only
>>in VFP, but in VB, and I suspect in other event-driven languages.
>

>Since the timer has its drawbacks (like overhead, firing at wrong
>moments etc), this way is an alternative - it costs you only firing
>thisform.refresh when you want to see the controls changing value,
>caption, color or whatever, based on the value of any other control's
>property.
>
>(I'm not sure who originated this thread - probably it was Dan, but then
>my initials are DAN, so it's half mine - I just got curious). HTH to
>whoever needed this.


Renarto Bertuol is the Original Creator.

This message if for Erik. Am I correct in assuming that when you are you using the timed event. Your having this timer fire once every 3 seconds for example. It would then call a procedure or method that would check these properties enabled or visible. If this is right, maybe you can answer the above comment about the drawbacks of the timed events.

Dan