>I am careting an instance of Excel using CreateObject command as follows
>
>oOle = Createobject("Excel.application")
>oOle.visible=.t.
>release oOle
>
>Why The release command does not close Excel.

Nabil

Trying your piece of code DOES close Excel indeed on my local VFP3/WIN95 install .. hope this helps.

Questions that may be hints for a solution : have you not other Excel code that would create more persistent Excel objects (opened un saved worksheets) or other VFP based references to your Excel app that could prevent your VFP Excel referenced object from closing ? are you using Excel 97 (automation has been
improve upon previous version) ?

I have anyway also encountered difficulties in similar situations in the past and also look forward to better understand and manage OLE automation from VFP.
My current experience with ole automation is that encapsulating the link-up to the "tried'nd proved" Excel friend works but remains fragile in production (error control) at least on WIN95.

My experience with MS OFFICE (97 version) up to now:
- Excel *** powerful, can do anything
- ACCESS ** equally impressive but for a specific usage (letting
users write their custom reports)
- WINWORD * difficult to use, badly documented, not a solid automation
server even in its 97 incarnation
- POWERPOINT .. not tried

Feed back by other UI members are welcome

François