Thanks for the additional reinforcement on that. I remembered something else as I considered this issue longer. I once had an excel automation problem that after 'x' itterations, every time the memory usage would do as John describes & take off like a jet after having stayed pretty level previously. The grand finale was that the screen would get really odd graphically... floating scroll bars out of place, just blotches of data here & there, there would be a brief blue screen error followed by an automatic reboot. All symptoms seemed to indicate that the video card memory was actually being invaded during this process! A tighter reign on my objects, similar to the model outlined in the previous message, stopped that issue! That was a WEIRD one to watch though.

>>Hi John,
>> Try being even more explicit by releasing the object after you're done with it in each iteration & see if it fixes your memory leak.
>>
>>

>>release oXLPage
>>

>>
>>Also, without seeing the actual code, I'm currious, the variable is called oXLPage, but what actual excel object is it? Application, workbook, sheet? I assume by the naming, that it's a sheet, well then is there also an application and workbook object that you have assigned to a variable out there somewhere? Could there theorhetically be Excel application objects out there that you did not explicitly create that continue to eat up memory? Perhaps try something like this & see what happens.
>
>My thoughts exactly. Despite caching and other dirty tricks, I think that re-creating an Excel automation object ina a loop would leak somewhere. I'd rather create ONE excel object and keep using it. My heaviest piece of automation code writes about 23 megabytes in about 80 sheets, where most of the sheets generated have two image objects on them, and takes about three minutes to run, and I haven't noticed any slowdowns. And I'm creating no more than just a couple of Excel automation objects in the process.