> I don't want lock file or record, I just want that foxpro did my 2 lines of code without interupt by a other line of code(MULTI-TASK) to prevent error.
>I will try with a exemple:
[...snip...]
>BAD
>----------------------------
>COMPUTER DID
>USER : SEEK IN TABLE USER1
>TIMER1 : SEEK IN TABLE USER1
>USER : GATHER MEMVAR

>May be I can resolve the problem if i used the same table open with 2 different alias But I don't know if with 4 or 5 different alias of the same table the performance will be affected?

Aha... what you have is what's called a 'resource deadlock'. Well, you're not really deadlocking but it's just about the same thing. The Timer1 procedure has a resource (a table in this case) conflict with your SEEK-GATHER procedure.

Don't worry, in a multi-process or multi-tasking environment, this is a problem everybody goes through, like puberty (s). The solution is to either:

a) just like you said, use different aliases or different views into the same table. If performance is a problem, you can try the various options for opening aliases (USE - AGAIN, etc.). You'll have to ask around, though, since I'm not very familiar with this. Or,

b) set up some kind of inter-process communication, in this case, you'd need a 'mutex' or mutual exclusion. Just use a global flag variable for this. If you need the details, I can give them to you.

Are we connecting, or am I totally of track here?