>Why is a timer an element of user interface??

Paul, I'm not entirely sure why, but I suspect that it's a matter of the interface to the Windows Event loop that causes the problem; the single best clear indication of this is that I've had standalone timer objects failing to trigger in a tight loop without the introduction of a DOEVENTS to the loop. Perhaps you have a better explanation for this behavioral anomaly?

>
>Vlad
>
>>The timer is an element of user interface, and you can't have any user interface to an in-process server. You might try using an API-based timer rather than relying on the VFP timer class.