>Erik,
>
>>What's so annoying about this is that it occurs seemingly randomly, and so might be _very_ difficult to trace down...
>
>Maybe the beginning of the problem is random, but once it starts on a certain EXE it keeps on, doesn't it? Doesn't it require stopping and starting that EXE to fix it?
>
>Seems to me that when it begins, one of the EXE's is bad and the others are still OK. When the garbage occurs, often another click sends the hit round robin to another EXE and you get good result.
>
>So, what goes wrong in that one EXE? That's the key question.

You resumed the situation pretty well.

We is being returned it the incoming data. I also expect that the process is being done. The reason I am saying that is that the delay to process the transaction is normal for what is being demand. So, I assume the transaction is done ok. However, the returned result is the incoming data.

What is weird into that is that I don't have anything which would do that type of stuff.

From what was told to me, it seems that the problem is from my code as no other WWC users have it. But, then, there is always a first one. In the meantime, I am still trying to find it.