> I think the reason madExcept didn't catch it is because BgExcept > caught it?
I bought MadExcept earlier this week and have been playing with it. It's really designed for applications without any try/except handlers, and misses anything already caught in that way, unless you add the function HandleException into each and every such except handler, including all components. At least that's my experience so far. But the traces it provides can be useful in locating the function causing problems. My main problem is GetHeapStatus which fails with an access violation on too many of our PCs. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
