>>Hi David,
>>
>>Just wanted to say to you, that you're not alone with this problem. On VFP Russian Club I found more than 6 threads on the same topic (e.g. Excel remains in memory/task lisk after loExcel.quit, release loExcel commands were issued).
>
>This is normal behavior for Excel (I think starting with Excel 2000). It stays in memory to facilitate loading it faster if you reopen it. I'm pretty sure it happens when you use it interactively, too.
>
>Tamar

I see. Still it may lead to unwanted effects, like in David's case. Also it's a usual practice to always close everything after the application had done with it. So, if VFP application used automation and the Excel stays in memory after that, the developer would feel, he/she did something wrongly...