>I have a set of com servers (exe's), of which 3 are active at any given time, 1 is vb6, the others are vfp5. the vb server creates the first vfp5 server. the vfp5 server then creates another vfp server, uses it, and discards it, then creates another (there is a pool of about 10 it chooses from). All goes well for about 40 to 60 of these swapps, then I get the message "visual foxpro cannot start there is not enough memory to complete this operation" when it tries to create one of the servers after discarding the former one. I used sysmon to monitor allocated memory, locked memory, unused physical memory, and page faults. I thought I would find some kind of creep in one of these graphs, but I did not see anything. Does someone know what could be the problem? I am using windows 95, have about 96 meg of RAM, and 12 gigs of hard drive about 1/2 full. I have run these servers several times in the past, and I know I have at least approached these levels of swapping before without
>problems. I am using the application.quit call to dump the vfp servers, and when I check task manager, the coms are gone after dumping.
>
>Of course my neck is being breathed down to finish this yesterday.
>
>Any help would be appreciated! TIA!

Now I am talking to myself! I recompiled everything in VFP6.0, changed the pool of 10 COM servers to multithreaded DLLs and ran again. Previously it crashed after ~40 swaps, now it crashes after ~110. So I have an improvement, but still crashing. Does anyone think that it would help to move to an NT4.0 maching with MTS? That is what we are going to try next. Please, anyone, we need help, or cyanide!