Tom,

Why don't you AddObject() the inner object instead of using this.oRef = CreateObject()? It'll make your cleanup life much easier, when the outer object is destroyed it'll get rid of the contained objects automatically.

>I have a nested class (i.e. a classs instantiated within another class and reference to the object stored in a property of the class). None of these commands-- RELEASE ALL, CLEAR ALL, CLEAR MEMORY-- triggers the Destroy() event of the nested class. In Visual Basic it's so easy (SET oRef = Nothing and it automatically garbage collects the nested object) but in FOxpro there seems to be nothing. Just setting the oNested = .F. does not trigger memory release, Destroy() and garbage collection. What am I overlooking?
>
>This is a big problem becasue the classes I am referring to are actually a FOxpro project which is compiled to a Multithreaded COM Server (DLL). I can use (createobject and release) the DLL in a VB project but not in an ASP web application. The web server (IIS) seems to be very picky about proper memory cleanup.