>>>Hey Sports fans.
>>>
>>>In VFP7 there are some fancy new DLL things. For example, there is a way to specify what DLLS you want to release with teh CLEAR command. It used to be CLEAR DLLS would kill them all, now you can do CLEAR DLLS dll1, dll2.
>>>
>>>DOn't know whats been DECLAREd? ADlls() will tell you all the DECLAREd Function Names, Function Aliases, and the libraries that contain them.
>>
>>In my mind this helps clear up a number of problems. You can now declare dlls and release it after you're done. Of course, I like to follow what I call "Mom's Rule": Put things back the way you found them. This makes that possible will DLL declarations.
>
>And this seems to be one of the cases where MSFT did what we asked. Remember the threads where we disputed the best practice on when to declare and when to clear the dlls, simply because they had to be declared one by one and cleared all at once.
>This does make our lives simpler - and the mom's rule would probably be something like "the method which declares the dll clears the dll and doesn't touch any others". We could also check whether the dlls was already declared, so we don't clear a dll which was still in use somewhere up the call stack.

My thoughts exactly Dragan. (Merry Christmas, BTW, to you and yours)