>>>>So your lights dim when someone flushes the toilet? ;-)
>>>>JLK.
>>>
>>>Yeah, well, that puzzled me already. It must be some dynamic optic connection. I mean, it looks like the FLUSH absorbes the light.
>>>Now I think of it, I have a few OPC COM servers around, and possibly some device's address is wrong. I'll look into that. Furthermore, does anyone have a good OPC compliant OCX for a toilet ? the one I am using now seems to Lock up the pipes. Could be the DCOM with the neighbours as well.
>>>
>>>Advice is appreciated !
>>
>>
>>mmm... maybe you are trying to push more data through the pipes than the bandwidth can take. I'd suggest doing an extra FLUSH or two miday through the data transfer! :-)
>
>Ahrrrgh ... Jerry, you brought me to the idea.
>At first I was thinking that the pipewidth didn't adapt to the bandwidth. Well, that's what you thought. HOWEVER, these pipes are not full duplex !!!
>So that's it. When too much is buffered, I guess at the other end things go just wrong. There won't be a call back in time, and the whole thing times out or so. So yes, a few other flushes during the day could help.
>I start with that tomorrow.

Wrong... this is OOP. You should say "I'll do that at my base class level and forget about the problem forever". So tomorrow find your oApp.Flush method and check its plumbing.

p.s. good that they're not full duplex. Wouldn't like the flushed data to return, or stay in a dirty buffer until rebooting.