Hmmm...I've been using Office2000 routinely under Win98SE and Win NT 4.0 SP5 and haven't seen that one. I usually do an oExcel.Quit() AND oExcel = .NULL.

Now screwing around with this on my laptop with Win NT4 SP5 I see that EXCEL.EXE stays in the Task Manager (is it a Tasker Manager on your machine?) after an oExcel.Quit but it goes away with oExcel = .NULL.

Hmmm.....try using both?


>...or Geo's continuing Adventure with OLE Automation"
>
>Hi troops,
>
>Could some try this and see if it's just me or if there's a problem with VFP 6.0 SP3/Excel 2000. This is on Win 98SE.

>oExcel = CREATEOBJECT('Excel.Application')
>oExcel.Quit

Now according to the documentation this should clear all instances of the automation server. However, when I go to the Task Manager, there's Excel plain as day. I've tried oExcel = NULL and RELEASE oExcel in addition to the above. No difference. In fact the only way I've found to purge the existence of Excel from the task manager is to quit VFP entirely. This makes me think that there's an internal problem with VFP releasing the object reference.
>
>The problem is that unless the instance of Excel is released, subsequent creation of any additional Excel servers cause them to be almost, but not quite, completely transparent when displayed.
>
>I'm out of ideas here. I've tried SendMessage() with WM_PAINT to fix the display problem. I've tried WM_CLOSE to shut it down with no luck (Excel GPFs and my entire machine goes into slow motion).
>
>I've searched the KB and can't find a reference to this.
>
>Any clues, suggestions or other information would be appreicated.