>>>>Some years ago SergeyB pointed out that a timer can be responsible for an incorrect value of _tally. I currently may have such a case happening in an application. What's your opinion? Should the use of _tally be avoided? Or should a timer-function that influences _tally reset it to what it was on enter? Or..
>>>>
>>>>Sergey's post: Re: _tally Thread #762047 Message #762137
>>>
>>>Save datasession context is necessary with AutoYield = .T.,
>>>except if the Timer lives into a private datasession.
>>>
>>>

>>>* timer event
>>>PRIVATE saveTally,saveWA,...
>>>
>>>saveTally = _TALLY
>>>saveWA    = SELECT(0)
>>>....
>>>
>>>SELECT (m.saveWA)
>>>TALLY = m.saveTally
>>>

>>
>>Lunardo, thanks for this useful hint. Are you sure that autoyield also affects the way timers are handled, which are not really activex/ocx controls, as to my understanding.
>
>autoYield is not aa specific ActiveX manage behaviour.
>AutoYield = .T. enable VFP to process Windows messages;
>this is as ( not equal ) to insert a DOEVENT after every VFP line of code.
>
>>
>>Do you personally save/restore _tally in your timers?
>
>When a timer can change _tally, active workarea, setting ...
>save/restore is not a choice but the only way for a write a correct program.

Interesting that it even affects _tally. I wonder what others here think of this.