>>Task Killer - http://www.rsdsoft.com/task_killer/index.php4 - kills it dead on the spot, no questions asked, and often kills what task manager won't. Also unloads services.
>
>Must we be happy with such a harsh killer? Tables may become 'corrupted'. I have corrupted here in quotes because I don't think that tables will get wrong headerinfo, but because they may loose their integrity when VFP was in the middle of some process like a programmed loop.

I have a case when a little side app (the one I use for maintaining my website) would error out in a C0000005, but even that doesn't produce a table corruption nowadays. And in cases where I had to kill some other app because it got stupid in a loop, also nothing happened - the last changes weren't written, I lost some of the session, but the integrity of the tables (and other files I had edited) was intact. It has become far more stable than in, say, VFP6 or VFP7. The "no new bugs" philosophy that was recently adopted by the Fox team adds to the stability as well.

As for the cruelty of the killer... well, it handles those cases that Task Manager just wont (but which get euthanized without a problem during system shutdown - so why not from Task Manager then?), which is why I'm using it.