>It is clearly documented that when AutoYield = .T., The instance of Visual FoxPro processes pending Windows events between execution of each line of user program code.
>Since it hasn't been proved as such, would you base your approach on a hunch that this is not true? If I understand corectly, Fabio is advising caution when dealing with this issue.

As to my understanding, the native timers are *not* windows events. Viv's test also suggests that they are not, because in that case the timers should have fired many times (autoyield is True in that code) during the for/next loop. Actually, they only started firing after that loop. I think the concept is not well understood by many of us.

>However, I don't use _TALLY in my code. IMO, RECCOUNT() or ALEN() is a much more worry-free aproach. My guess is that the purpose of _TALLY in VFP is to provide feeback *during* tallying operations. Thus, I wouldn't consider _TALLY a reliable value once the operation is completed.