>>>Any kind of loop that has processing code and no wait states.
>>>
>>>Tamar
>>
>>Let me clarify. Say I have a following pseudo loop in a timer event:
>>
>>
>>do while <Some Condition>
>>
>> DOEVENTS
>>
>> <SQL Select statement >
>>
>> <Call to Print a short Report>
>>
>>enddo
>>
>>
>>Putting this DOEVENT in the place where I put it above would be advisable?
>
>It's not a wait state, i.e. not a "system is waiting for user input" state - it's a "in case user is doing something else, let's stop for a moment and give Windows a chance to react".
>
>There's another definition of a tight timer code: anything that has a chance to run longer than the .interval of the timer. Or anything that makes the timer code actually consume most of the processor time. Or anything that will perceptibly slow down the rest.
>
>I mean, timers are fine as long as you don't notice them :).
Thank you, Dragan.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
