>>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.
Do you personally save/restore _tally in your timers?
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
