I never heard of one.<BR><BR>You might want to do some manual checking of the code and look for any objects which you might not have closed. Free objects from memory as soon as you are done with them.<BR><BR>Also pay attention to the cursor types. Make use of only relevant cursor types. <BR><BR>You can save a lot on memory resources by paying attention to small details like that.
There are definitely tools available for detecting this. But each of the ones are priced very heavily and I cannot afford that. I wanted any one which is a shareware version and free to download.<BR><BR>Anyway thanks for the help.<BR>Try http://www.glowcode.com<BR><BR>Regards,<BR>Vinay
.... are called 'good coders', and they're available at quite reasonable rates.<BR><BR>the BEST BEST way is just to code so that the possibility of leaks is minimised as much as possible. some understanding of Windows' basic administration tools is a good start, as is a scrupulous attitude towards your code, a regimented code/test cycle and experience.