Bill

Are you controlling the web page through com? If so, you can check to see if the page is complete instead of using the timer.

>I do that, but that's not my problem. Sometimes the browser ties up all the computer's resources trying to download a web-page. It doesn't stop the timer from counting down and sending instructions to the computer to execute the process. The computer just doesn't execute the process because it's busy trying to download the web-page. As soon as the computer is through downloading the page it then executes all the code that has stacked up. And sometimes that's over a dozen calls to the same timer event.
>
>Also there is no way to disable the timer, because the code to disable it would be in the process that's waiting to execute.
>
>>Hi Bill
>>
>>You should always disable the timer when it calls a process and then turn it on when completed.
>>
>>

>>procedure timerevent
>>  this.enabled = .f.
>>  thisform.somemethod()
>>  this.enabled = .t.
>>endproc
>>

>>
>>
>>>I'm using VFP 7.0
>>>
>>>I have a timer with an interval 250. Sometimes when I'm trying to open a stubborn page in the web browser control my timer events stack up. Then when the page finishes loading, all the timer events execute one after another.
>>>
>>>Is there someway to get the timer to quit stacking up the events and just trigger it once when the page finishes loading?
>>>
>>>The timer is primarily just checking to see if the page has finished loading (DownLoadComplete() and DocumentComplete() are not reliable enough).
>>>
>>>TIA