Nigel:

Well, that did it!!! By giveing a little "intelligence" to my polling routines, I can now set the timer interval to even 100ms and not have a slow down - had it on all night.

Thanks for the great advice.

Mal

>Maybe you could get the poller to check if the COM server is busy before requesting data - if yes, don't check data this time. If no, call as normal. Adds a bit more intelligence to the app. Also prevents excessive calls.
>
>>Nigel:
>>
>>Thanks for your help. What you say makes great sense. I WILL play with the interval, though it has to be close, very close, to a second (2 at the most).
>>
>>I'll post my result.
>>
>>Mal
>>
>>
>>>Change your interval. I'm sure it takes a good second or so for the COM server to do it's stuff. What seems to be happening is that you're getting a build-up of calls to the COM server. Does it really need to do this every second? Can it do a poll every minute (or even 30 seconds). Any delay in the COM/OLEDB will generate a lag. Do some time testing to see how long it takes at it's slowest and set your timer interval greater than the resultant time.
>>>
>>>>Hi All:
>>>>
>>>>Have an application that polls a COM server (on the local machine) every second. The COM server then retreives RecordSets or Strings from SQL SERVER 7 (stored procedures), via OLEDB, every second.
>>>>
>>>>My problem: The application runs fine at first. However, when I leave it running over night, the polling is no longer every second but every 3~4 seconds (despite it's timer interval at 1 second), the mouse works but the hour glass persists, and clicking on buttons takes a long time to register: about a minute.
>>>>
>>>>What could be happening here?
>>>>
>>>>TIA
>>>>
>>>>Mal