>Gary,
>
>>Does Rick accept that this is a WWC problem? Are you at odds with him on this, hence this somewhat "public" proclamation on the UT and not the WWC message board?
>
>I can't speak for Rick, but from my perspective, the key is that when problem occurs, only one of UT's multiple EXE's is affected, meaning that either that EXE itself has lost the ability to properly communicate back and forth with the wc.dll, or wc.dll has somehow lost the ability to communicate with just that EXE, or both.
>
>Something somewhere is getting scrambled in the connection between the dll and that particular EXE. It's just a question of narrowing down the investigation to the circumstances that bring on the problem.

Well, as I mentioned, we have isolated the situation. When that happens, it does not even goes in the WWC VFP server. So, it is at the DLL level.