>The first timer event occurs after the first time slice. So, one solution is to set your timer interval big enough to be sure the other event is finished. You can reset the timer interval in the Timer event, first time it occurs.

Yes, this was working when I tried it but I need to avoid that. I am exchanging hundreds of transactions in a few seconds from both applications over the TCPIP using socket and I don't want to put a time lap to obtain a result from 2 seconds to 25 seconds as it was when I increment the interval a little bit. Also, we can never be sure the interval will be big enough. I need something which is bullet proof. There must be a protocol mecanism to handle that kind of behavior.

>Second solution: use a flag, if possible.

Something has to set the flag and it need to be done at the end of the first event so back to square one.

>Also: Activate your timer as last action in calling event.

This is what I have.