>Yupp, and FYI controlling WorkingSet is also needed when automating IE (both from VB6 and vfp) for a longer stretch of time, as IE will just gobble up process space. Discovered it long ago, plus a quick dirty check for windowed instances like IE:
>if you minimize the window (manual or programmatic - makes no difference) the WorkingSet will be trimmed, similar to vfp's wait window calling a doevents, so you can test in GUI if you see something weird in processes on tasklist...

I had a situation where I had to keep an instance of browser control (i.e. IE COM object) in a container, letting the user navigate to a website (where I had to provide navigation, some checksum is expected in the url), and when the user logs out from there, pull the data she created over there, and then show them in this same container. Then there was a request to make this display a bit neater, so I created another instance of browser control for display... and then I had it working smoothly for weeks, until it stopped. Either one wouldn't go invisible, or leaked through other controls, or wouldn't go visible again. Very nasty, unruly and chaotic, in that particular order.

The solution was to not even try to hide minimize or anything - just kill it when not in use, make new when you need it. The code was already there, I only needed to call it every time, not just once. And they lived happily ever after. And the memory consumption stayed low.