OK, thanks for the help. I don't know if the lack of centralized error reporting "place" is a "marketing" decision, but just to complain a little: I have had this product for two years and was never made aware of the problems which have fixes. I just happened to stumble into your ftp site and found out about them. It seems like a bad idea to make the client go digging around in the knowledge base to discover this stuff, especially since the memory leaks are not reported by the standard VC++ IDE, you have to use purify or some other commercial product. What is worse, having someone�s control system go down in release or admitting there are some problems up front? I think developers would understand the spiral cycle of software rele
ase.