>>
>>
>>Are you sure there are no instances of the COM DLL? Remember that IIS will hold onto the DLL, which is why you need to kill the IIS Service to update the DLL.
>
>Oh yes. the DLL remains loaded. But I thought that table access was scoped to each instance of a COM object created by the DLL (e.g, by using the server.createobject() call from ASP). I thought that when a given VFP COM object was destroyed, that its _entire_ datasession was also destroyed. I thought that the DLL nevertheless stayed loaded, serving as an "object factory", and when next called upon to instantiate an object, would create an entirely new global data session for that object. What's the truth?

You have to explicitly close the tables.