>>Basically, with some rare exceptions, CLEAR DLLS should never be used in a program. (Because you don't know all the pieces of program that declare DLL functions and which assume that those functions are "there"). In order to protect yourself against other programs which may CLEAR DLLS, always DECLARE your DLL functions right before their use (or, at least, in the same function/proc/method). One exception is GetLastError() which must be declared before the use of other DLL functions for which you want to retrieve the last error code.
>
>Hi Vlad - I think I fall into the "rare exception" category - I have a small program (exe) that runs a launcher and a few other things, and contains a number of DLL declares, before running a larger EXE. As a matter of tidiness, I want to clean up all the DLLs it uses, but don't want a complete CLEAR ALL, either. So CLEAR DLLS does the right job for this situation.
>
>But I just wanted to make sure the CLEAR DLLS didn't wipe out the main EXE DLLs, since one of the functions of the small EXE is that it can be re-run while the larger one is running, and aborted part way through if the large app is already instanced. IOW, one of its duties is to check for more than one instance. If this all makes any sense...

Bruce, that depends. Does your launcher EXE start the second EXE with a DO second.EXE or RUN second.EXE. If it's RUN, no problem, they are running separately. If it's DO, then they're both running within the same copy of the runtime.