This could also be caused by known problems of certain versions of ADO/MDAC. Just do a MSKB search on "kbado memory leak" and you will get a number of hits explaining different scenarios and ADO versions.

Just a thought,

>After upgrading the framework to version 2, I started noticing a problem with my middle tier servers. The components were running out of memory in a matter of hours. It seemed that the COM+ service was not releasing memory for some reason.
>
>I finally tracked to problem down to a line of code that was added to 2 methods in version 2.
>
>This method is called from ExecuteQuery and Save.
>
>This.CloseConnectionObject( toADO )
>
>This was not called in version 1. It would appear that there is some sort of memory leak with toADO.oConnection.Close(). Does anyone know the behavior of this method, and why calling it wouldn't release the memory? It sounds like it sends the memory back to a pool instead of releasing it? Maybe VFP can't handle this way of reusing memory in the COM+ service?
>
>Thanks,
>
>Dan
>MCSD