>Visual FoxPro is NOT a multi-tasking environment. The program itself seldom has more than 2 threads running, even under Win95. From my experience with VFP, an event (such as the Timer event) cannot be triggered while a procedure is executing. So when one procedure is processing code, an event cannot do a SEEK and disrupt the record pointer. Anyway, FoxPro is not the environment you want to be implementing too much multi-tasking -- Timers are great, but they have their limits.
>
>Hope this helps,
>If you still have a problem maybe you could be more specific.
>Peter

No Peter your right on the spot
Thank's for your help
Rock