David,
>
>Sounds like a good use for a project hook to me... scan the files and fire the programmer that ever puts a CLEAR DLL command in their code. *L*

Good idea, except I'd have to fire myself.:-) I've got some stuff that does issue a CLEAR DLLS. Of course, it's a testing module that I'm using with a COM server I'm writing. If I don't issue CLEAR DLLS when the object's Destroy method fires, I can't re-compile the COM DLL.

>>Sometimes it can't be helped and as much as I hate wasting CPU cycles, I hate trying to chase down where and why the CLEAR DLLS command was issued in a project.< s >