COM over the Network and VB

[LabtroRob]

Hi Everyone,

I'm running a third party application that runs scripts under the parent ID. The problem is that in these scripts, I create objects, and use them.

The actual DLL's are sitting on a server over the network. The problem is that when I'm finished using them in the VB script, and actually exit the program, if I look on the server, the DLL's are still open.

I'm using the following:

Dim Object as DLLWhatever
Set Object = New DLLWhatever

'Code

Set Object = Nothing

I'm wondering if there is a way to more actively kill these connections, other then setting them = nothing.

[aidan]

I had a similar problem when I made an ActiveX component for an ASP page. Once the page had been requested, I had to restart my computer, (which was running IIS) before the DLL was released. I'd like to know how to avoid this too.