Thanks for the whole explanation. I am not explicitly calling SetComplete/SetAbort.



>Steve,
>If you don't call SetComplete/SetAbort then your object has state and remains in memory until you release it. If that is the case, then you may be able to create an instance of the MSXML2.FreeThreadedDOMDocument and store it to a property of the VFP object in the Init or a mthod called from the Init. You could then reference it anywhere in your object. It wouldn't be released until your object was released and you performed the cleanup.
>
>If you are calling SetComplete/SetAbort in your VFP object to provide for statelessness then you are out of luck. The proxy object may remain in COM+ forever, but the actual VFP object is continually created and destroyed (thereby creatig and destroying the XML object).
>
>HTH.