Thanks!
So, it's allways a good practice first set to null and then release?
>In this case you must make sure that you release oWorkbook also, since it holds a reference to oExce. And you must release it before oExcel.
>oWorkbook=.null.
>oExcel=.null.
>Relase oWorkbook
>Release oExcel
>
>>Hi.
>>I've created an Excel object named 'oExcel'.
>>Then, I've loaded a XLS file and read information from it.
>>When done I've issued 'oExcel.Quit()'.
>>I've noticed in the Windows Task Manager that the process
>>'excel.exe' didn't unload from memory. To unload it I've had
>>to issue an 'Release oExcel'.
>>Is that the correct way?
>>Here is the pseudo-code
>>
>>
>>vFile = 'my file'
>>oExcel = CreateObject("Excel.Application")
>>oWorkbook = oExcel.Workbooks.Open(vFile)
>>
>>... bla bla bla ...
>>
>>oExcel.Quit()
>>RELEASE oExcel
>>
***
TONY Nascimento
*****************
"Your mind is like a parachute. It only works if it is open" - Anthony J. D'Angelo
"The desire to know is natural to good men" - Leonardo da Vinci