M
mookashi
hi,
i was going through the outlook exchange site and i happened to rea
something which prompted me to change a bit of my code.
it said that the inspector and explorer objects should be set t
nothing in their respective close events and not anywhere else such a
beginshutdown or ondisconnect events. otherwise outlook may show som
error messages and it may continue to run in the background.
while it was true that i was getting some memory related errors when
closed outlook, it was definitely not running in the background.
however i made the necessary changes and now it seems to be the othe
way around. the memory error seems to have vanished but now outloo
somehow still remains running in the task manager. how do i get to exi
outlook completely. or is there any way i can terminate this proces
through my vb code.
thanks
i was going through the outlook exchange site and i happened to rea
something which prompted me to change a bit of my code.
it said that the inspector and explorer objects should be set t
nothing in their respective close events and not anywhere else such a
beginshutdown or ondisconnect events. otherwise outlook may show som
error messages and it may continue to run in the background.
while it was true that i was getting some memory related errors when
closed outlook, it was definitely not running in the background.
however i made the necessary changes and now it seems to be the othe
way around. the memory error seems to have vanished but now outloo
somehow still remains running in the task manager. how do i get to exi
outlook completely. or is there any way i can terminate this proces
through my vb code.
thanks