>>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.
>
>Not sure if it will work in this case, but you could add an additional method in your COM server that issues a Quit. Call this method and then set the variable to Nothing. Note: Haven't tested it. Good luck!

Don't know if this would do it or not, but within VFP it seems to work. In the Destroy event, issue CLEAR DLLS.