Well, I have to agree with you to an extent. But, vbscript offers all it could offer 
. However, QTP's log has pretty elaborate error reporting if you use the Reporter.ReportEvent function or even if the object failed it will report the reason. You may want to work on customizing QTP report so that you can add the Err.Values in there.
And for the too many If statements, well, it is basically the net you have to weave to catch the errors. When you are done weaving, what looks like a clutter actually turns out to be an well layered trap. Trust me, it does not slow down execution.
All that said, Error Handling is an challenge and if you could find an impoverished way please do post it across.
. However, QTP's log has pretty elaborate error reporting if you use the Reporter.ReportEvent function or even if the object failed it will report the reason. You may want to work on customizing QTP report so that you can add the Err.Values in there.And for the too many If statements, well, it is basically the net you have to weave to catch the errors. When you are done weaving, what looks like a clutter actually turns out to be an well layered trap. Trust me, it does not slow down execution.
All that said, Error Handling is an challenge and if you could find an impoverished way please do post it across.
Basanth
Give a fish to a man and you feed him for a day..Teach a man how to fish and you feed him for life.
Give a fish to a man and you feed him for a day..Teach a man how to fish and you feed him for life.