Thanks Rick,

Thanks for the help.

The callback simply increments a counter that is serviced by a timer that runs in the server. No parameters are passed. The server is not showing a problem with increased CPU or memory usage so I'm assuming that the cause isn't due to the timer.

If I could figure out what sort of VFP activity could cause CPU usage and bytes allocated to slowly rise over time I would have a place to start looking but all the tests I have done to try to cause this behavior have been mostly unsuccessful. It seems like a memory leak to me. I thought I had caught it when one of my tests indicated that there was a VFP memory leak in passing large strings to functions. I talked to Calvin about it and tried some of his suggestions. Finally a coworker suggested checking the Paging File Size. I ended up setting my paging file size to "System Managed" from "Custom" and that got rid of the 'leak' which tells me that there was some sort of memory fragmentation going on. Fixing this didn't fix the greater problem though.

I am starting to fear that either VFP isn't fast enough to keep up with the communications demand or that there is a resource leak in my communications library.

Thanks again Rick,

Steve