>>>Hi All,
>>>
>>>I have 2 EXEs in the same folder. I start one which communicates over the internet to a back-end server to retrieve data. The other exe displays that data. They both use the same set of VFP9 dll files.
>>>
>>>If the program that does the internet comms gets hung up waiting for some comms issue then its title bar can show the usual "Not responding" suffix. Thats ok. The problem is that this affects the second exe file which also becomes unresponsive. Why? Is it because they share the same set of VFP dll files? Would making each exe use its own set of VFP dll files resolve this?
>>
>>How does the 2nd EXE display the data? More specifically, how does it update its display? Does the 2nd one rely on something (say, a table) that the first one may have locked while it's waiting/hung? Does the 2nd one go into any sort of tight loop, repeated timer calls that aren't completing etc.?
>>
>>Two separate EXEs should not affect each other. If they do, there's some shared resource that's being locked, blocked or otherwise hogged by one, and that's affecting the other.
>
>If it's a COM .DLL, it most certainly can effect multiple .EXEs. Oh what joy it is when it effects 300+ workstations!

True, but I thought from reading Jos's other messages, this was not the case. IIRC he's using Cryptor; he did have wwIPStuff linked into the 2nd one but wasn't using it there, and I think he is/was going to remove the reference from that EXE.