Better error handling in CTD

[Michel de Becdelièvre]

I already asked for that before the NG crash, and got no answer anyway,
except from a few other dveloppers wha needed the same thing...

I'm quite satisfied with the way SQL errors are handled (I'd only like
to have a way to display the values of the variables used in the query)
BUT I'm very dissatisfied, with the way CTD2000 handles the other errors
: if you are in a MTS component and you get, for example, an "array out of
bounds" error it locks the IIS server (apparenty it is trying to open the
"array out of bound" dialog box, but since it does not have the support for
graphics, it hangs), and you need to reboot the server.
Great stuff in a production environment ! One user client error crashes
all the other users !
Do not tell me that this kind of bugs should never happen, they do.
Besides being forced to reboot the IIS server whenever you make this kind of
error also makes the development effort very slow.

So I'd like to be able to trap this kind of errors. I do not need to be
able to to a lot of things after :

1) want to be able to quit cleanly (no hang up)
2) even better, I want to be able to signal the calling program that I'm
in trouble (to be able to implement the error handling interfaces of IIS)
3) I would be great to be able to open a file and write an error
message.

If I'm not at least able to do 1) the MTS capacities of CTD are USELESS.