Hi

Can somebody please give me a good reason why Close function of certain
things like forms or word application obejcts should be used rather than just
killing them of as a process?

The thing is Im working with word objects and it is just such a pain because
when ever PC slows down you start getting errors like: Call was rejected by
callee. (Exception from HRESULT: 0x80010001 (RPC_E_CALL_REJECTED))

But if you close (for example) word app with process killer it works just
fine (no questions, no problems etc... :))

--
Government sucks, but the beer is still good!

RE: Why Close when you can Kill? by JeanGuyMarcil

JeanGuyMarcil
Wed Apr 09 09:53:03 PDT 2008

"Antinsh" wrote:

> Hi
>
> Can somebody please give me a good reason why Close function of certain
> things like forms or word application obejcts should be used rather than just
> killing them of as a process?
>
> The thing is Im working with word objects and it is just such a pain because
> when ever PC slows down you start getting errors like: Call was rejected by
> callee. (Exception from HRESULT: 0x80010001 (RPC_E_CALL_REJECTED))
>
> But if you close (for example) word app with process killer it works just
> fine (no questions, no problems etc... :))
>
> --
> Government sucks, but the beer is still good!

Re. Subject line:

Isn't that he motto of NRA Salesmen?



Re. Enquiry:

Killing a process may create other problems if the processing was not
complete.
In my opinion, it is like a lazy way out... You should investigate why
errors are generated and either code so that those errors do not shopw up or
handle them with error trapping.
Now, if you are 1000% (Yes, 1000, not 100!) certain that all processing is
complete, then I guess you can kill the process...


RE: Why Close when you can Kill? by Antinsh

Antinsh
Wed Apr 09 22:15:01 PDT 2008


> Isn't that he motto of NRA Salesmen?

lol :) It could be.