>>>Might be interesting to preface your code above with CLEAR RESOURCES, see if it makes any difference.
>>
>>Testing as we speak. Just to note that the memory consumption was flipping between 18 and 20 M when it launched. But then I don't remember what it used to be - should perhaps run the old version for a while. Last I remember it displayed about 40000 images before I stopped it, and then the next day the system was unstable. We'll see. I'll run this to a similar number and see what happens.
>
>After a whole day, it's still getting down to 22M, depending on the size of the currently displayed images (runs separate forms for each monitor). But then I don't think it caused trouble previously either. At one image every 4 seconds it has clicked 20900 so far... though there should have been more. And it wasn't getting any new images to detect, measure up and store in the tables... perhaps that's what's troubling, as I probably have to use the iPicture interface to measure the width and height of each so I can know their orientation (right monitor is upright, so portrait shots are sent there). Perhaps that's the cause...

If you're auto-scraping web sites (with IE/WebBrowser control?) there could be lots of other reasons for what you were seeing.

A while back I took an introductory PowerShell seminar. One of the things we touched on was downloading web page content ( Google [powershell download webpage] ). PowerShell is server-grade, IE is not.