Tamar,

>>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.

This seems a strange 'strategy', given my observations with MS Word ('97 in my case).
With Word97 I have always noticed that it may take a bit to load the first time, but after exiting (and no longer seeing it in the Task List) a restart (i.e. starting it again normally) is virtually instantaneous, particularly if I have done not too much else in between.

As the author of the "Who's computer is it anyway" article way back when, and considering that explicitly issuing QUIT or RELEASE is done, I would expect you to indicate some distaste for this kind of changed behaviour.

Does MS note this change in its documentation? Does MS supply some means to explicitly cause its removal from RAM and is it well documented? If so, why would they not have left QUIT/RELEASE alone and invented some new means to accomplish what they wanted?
Jim


>
>Tamar