🚀 go-pugleaf

> I still don't understand what David (the op) is trying to achieve.

The DLL sends messages to my app but I don't send messages back. If the user 
exits the app then I would like to warn the user that there is still a DLL 
trying to communicate with it before the user exits. Therefore I need to 
know if the DLL is still in use.

Actually I do have access to source code for the DLL so maybe I could do 
something from the DLL end. I asked here once whether or not you could send 
messages to a DLL and it wasn't a simple proposition either.

regards
david




"Boba" <Boba@somewhere.world> wrote in message 
news:443bd8e0$1@newsgroups.borland.com...
> "Dennis Jones" <nospam@nospam.com> wrote in message
> news:443aac3c$1@newsgroups.borland.com...
>> ...
>> There's probably an easier way, but the first thing that comes to mind is
> to
>> enumerate the modules loaded by each process currently running on the
>> system, looking for the one you're interested in.  If you don't find it,
> it
>> isn't loaded.
>>
> been there, done that...
> if a module is not curremtly beeing used by any of the software visible to
> UI via what you're talking about, there are still tons of software running
> in below UI level that may still need those modules in which case you may
> think the module is not in use: try to delete... if it fails - keep 
> digging
> deeper.
> I still don't understand what David (the op) is trying to achieve.
>
>