cumbersome coding style (1 Viewer)

[gemma-the-husky]

I can't offhand think of an example of this, but from time to time, I want to do something, and carryon whether or not I got a run time error - but I can't just use an onerrror resume next, because the error will need some action.

so I end with this sort of thing

...
     on error goto failed
     execute process that might error
     goto continuepoint

failed:
     cleanup after error
     resume continuepoint

continuepoint:
      carry on

is there an easier way to do this. would try .. .catch be a better way of managing this sort of thing? I have never really looked at try .. catch in detail.

 

[CJ_London]

I sometimes use this when some in line correction can be done

 on error resume next
 [I]line where error may occur[/I]
 select case err.number
   case...
   ...
 end select
 on error goto 0
 ...
 ...

or

 on error resume next
 [I]line where error may occur[/I]
 if err.number<>0 then
   ...
   ...
 end if
 on error goto 0
 ...
 ...

 

[vbaInet]

Similar to CJ's:

...
[COLOR="Blue"]     on error resume next[/COLOR]
     execute process that might error
[COLOR="blue"]     on error goto continuepoint[/COLOR]
     carry on with other code

failed:
     exit sub/function

continuepoint:
     handle other errors
     cleanup after error
     resume failed

 

[JLCantara]

I can't offhand think of an example of this but you know that the error will need some action.
Are you a clairvoyant?