Hi!

What means "Does not works"? How you SEE it does not works? In other words, what's your observations about its behavior.

Also, thet Timer event code should look like following:

local lnOldInterval
lnOldInterval = this.Interval
this.Interval=0
this.Enabled=.F.

... do your process code here

this.Interval = m.lnOldInterval 
this.Enabled = .T.
this.Reset

All above to assure no cashed timer events are stored internally for your timer control. Also, did you tried to debug your app in "visible" mode? To do so run servise under your user account and allo it "Interact with desktop" (option for service properties). In the APP set _Screen.visible = .T. Then see what happens. If your APP shows dialog box, you will see that - this also might be a cause of hang up. VERY popular hang up of this kind is "open table" dialog box when you use some command on the work area without any current table open.

HTH.

>I have created 3 Application in VFP 7 and I install it as a Win2K service. All of the applications have d same frameworks. It has a custom class then a timer to run a particular task in a given interval. 2 of this service works will but the other one does'nt. The only diff between this one that does'nt work is that it has a bigger and longer process than the other, coz it writes larger amount of data to the table.
>
>Can anyone give me the limitations or more details in the performance of VFP Applications as an Win2K/NT Service.
>
>Any suggestions and response will be appreciated.
>Thanks...
>VIRGIL