That is very close to the question I asked when someone started telling
me how wonderful all this structured stuff is vs. assembler where
everything is everything and you can do what you want. Data is data and
is only a character if you ask it to be and is a number if you ask it to
be without any change in the actual data or its location. If you
reference it with a math operator, it is a number, if you printing it on
paper, it is a character.
The actual answer is that you have to set all the traps and every
routine has to know what is going on with all that it has called and it
is a mess sometimes! Someone down deep gets an error and has to back
out all these levels and you have to code and be ready for it all the
way down so you can come all the way back and sit ready for the user
again.
People seem to think that all this plumbing is the greatest thing but I
will stop liking branch statements when the hardware stops using them!
And the folks who think that "On Error Resume Next" is useless needs to
read a few books by experts. The new Try/Catch business does NOT do
everything that needs be done. Resume Next is still necessary at times.
If I delete a file and it is not there, who cares? I just resume next
around it and I never know if it was there or not. I want it gone, when
I get through it is gone, mission accomplished. Yes, there can be some
other errors but those can be caught in one testing pass and then all is
done.
Mike
On Thu, 5 Jun 2008 03:07:55 +0100, in
microsoft.publi c.dotnet.langua ges.vb "John" <in**@nospam.in fovis.co.uk>
wrote:
>Hi
I have a button which calls a method which in turn calls another method,
which in turn calls another method. Let's say in the third method an error
occurs and it is no longer possible to continue, how can I dump everything
and come out of everything waiting for the user to press the button again to
do the process again?
Thanks
Regards