Callback? That raises all sorts of flags.

Is it possible these callbacks result in a circular reference for each call? If you pass an object out of the COM object and don't release it the COM object would stay loaded even if you release the reference to the COM object...

The thing to do is keep an eye on object handle usage. If this value keeps going up (as I guess it would) you can use that to try an pin-point where the counter goes up and not back down when you call your callback component for example.

Circular references are the camel that will break VFP's back VERY QUICKLY...

+++ Rick ---



>Paul,
>
>Sorry about not being clear on these points.
>
>The server is written in VFP and does no poling or looping to speak of. It is an EXE that runs on the server box and instantiates the COM server which is also written in VFP. The COM server calls back to the server via a callback that is established between them. It uses the callback when it gets any packets that need to be processed or sent out to connected clients. The COM server uses an activeX control that was written by a C++ programmer who works for us using a communications library to do the communications. Admittedly, the OCX might be the problem but I can't tell if it is using the monitoring tools that I have available to me. (ProcessExplorer by SysInternals) I am trying to rule out VFP as the problem since I know it well.
>
>Thanks again for your help.
>
>Steve