>I have a Foxpro comserver that I invoke from a VBA macro. When I set the reference variable in the macro to NOTHING, the dll file remains tied up. I have to exit the application program with the macro before I can update or delete the dll file. Is there a way to tell the comserver to release itself before I set the reference variable to nothing. The comserver is based on a session base class. Thanks.

It a problem with the caller not VFP. Set objvar = Nothing should release the reference unless there is another reference holding it. Just out of curiosity, what application is calling the COM server?