Hi,

I though placing all my code in the timer() method will do. Why
do I had to call the reset method ?, please advise me on this.
I just had my timer event trigger every 1 minute.

>Okay:
>It would be easy to say VFP5a may get sick sometimes (I dunno) - VFP6 w/ Visial Studio SP3 is what I use. I don't recall if timer is standard class or OCX with VFP5. When your routine issues a timer.reset, does it set timer.interval to 0 (zero)?
>
>>Hi,
>>
>>Thank for your advise and suggestions.
>>I am still using VFP5a with service pack 3
>>I had my application trigger time for timer set to 60,000 ticks and
>>the timer disabled when updating the dbf file, before turing it back,
>>but it still give me error, plus under NT task manager, the memory usage
>>seem to increase, thus my conclusion of memory leakage.
>>I am using timer, grid and command button control only. Please advise.
>>
>>
>>
>>>Let's see!
>>>Your using the VFP6 timer control.
>>>
>>>1) You have it set to read and write to DBFs at 1 minute intervals.
>>>That is 60,000 timer ticks. 1 second is 1000 timer ticks. So assure that your process interval is triggered every 60,000 ticks.
>>>
>>>2) When the process is triggered, you may want to reset the timer (turn it off), until the process finishes. When the process completes, you could turn it on.
>>>
>>>So make sure 1 minute = 60,000 and look at possibly using a timer 'reset' when your process is triggered, and let us know how it worked out.
>>>
>>>Terry
>>>
>>>
>>>
>>>>Hi,
>>>>
>>>>I can't open the 03 dbf files in shared mode as I may need to delete
>>>>all the records inside them.
>>>>My application seem to causes memory leakage, crashing itself out.
>>>>Please advise.
>>>>
>>>>
>>>>>>Hi,
>>>>>>
>>>>>>Thank for the advise.
>>>>>>However,my application just do the following below
>>>>>>
>>>>>>01) open 03 permanent dbf file in exclusive mode
>>>>>>02) read 01 permanent dbf file and update the records into the above 01 dbf file
>>>>>>03) read & update all records every 01 minute.
>>>>>
>>>>>Maybe the interval sessions appear like 'share' users. Have you tried opening 03 as a shared file?
>>>>>Terry