You said in another thread that you've done C++ development. If so, you should know the answer is nope, you can't do that. When you get memory leaks, memory gets in a corrupt state. There is no way to say what issues it caused. What if it writes into the memory used by another application? How does it reset that?

>Does anybody know if issuing CLEAR DLLS will clear the dll in such a way that any memory it leaked during execution is reclaimed before the app instance truly terminates?
>
>I have a DLL that does this from time to time. I'd like to just CLEAR DLLS it out from time to time by name and then immediately re-load it --- if this would work. :-)