Hi Jim,

>Each time I hit the server, I can watch the memory usage in the Task Manager continue to increase by a few hundred K for my server app. As I look at the log entries I see the following.

If you're running a multi-use EXE that's to be expected. Each instances
requires some housekeeping overhead even when it's reusing the VFP
runtime. What you're seeing there is your code/EXE loading into memory.
Again, single use servers will make this more obvious and more efficient
even though they'll use more memory.

>The Reset command returns the Dispatch value for the original instance which then triggers the Destroy event for each of the Instances that had stacked up on me. Startup is the method which requests the initial page, the other events represent different form requests on that page.

RESET just cycles through the entire list of IDispatch pointers. It's a linked
list and it just walks the list releasing servers. The VFP servers do nothing
other than attempting to unload (which it won't if the server is hung or
busy).

I haven't tested FoxISAPI for memory leaks - as you might expect I don't
use it much :-} I just know how it works since it's got a bunch of my specs
in it and I've dug through the code for useful pieces that I might be able
to use in WC. WC uses a different pool manager approach though, and
it is definitely *not* leaking memory with IIS :-}