>>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
>
>I would think that the activex could be the problem. I know for a fact that the Winsock Activex from Microsoft leaks memory like a sieve. I once tried to use it in an enterprise chat app and it nearly brought the server down. After a while you could actually see the memory usage going up in the task manager.
>
>Try running the EXE and COM without the Activex and see if there is still a problem.
>
>Otherwise you need to add a timer and use the Win32API to release memory at intervals.

sys(1004) or my memory fails on this one?