IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New That was a joke
That was a joke, not a programming idea. On Error Resume Next tells VB to simply continue with the next step when there is an error. This causes all sorts of havok when there is a real problem.

But if you want a really global error trap, then either put the entire program inside a try/catch block or a global On Error statement at the start.

There isn't much you can do in VB if you catch errors at that level though. All you can do is present some formatted error information and quit.

Jay
New For certain techniques, it works.
Specifically, the practice of manually checking ErrCode after steps that could catastrophically fail. It's a bit lazy, though for some types of code, the risk of an uncaught error is suitably low.

Wade.

Is it enough to love
Is it enough to breathe
Somebody rip my heart out
And leave me here to bleed
 
Is it enough to die
Somebody save my life
I'd rather be Anything but Ordinary
Please

-- "Anything but Ordinary" by Avril Lavigne.

     Access: Runtime error 91. - (acagle) - (22)
         I think that one means... - (pwhysall) - (10)
             Re: I think that one means... - (acagle) - (9)
                 From the 10 Commandments of C Programming: - (inthane-chan) - (8)
                     So. - (acagle) - (7)
                         In VB? - (JayMehaffey) - (5)
                             Re: In VB? - (acagle) - (4)
                                 You can use On Error GoTo - (ben_tilly) - (1)
                                     That's still the way - (Steven A S)
                                 That was a joke - (JayMehaffey) - (1)
                                     For certain techniques, it works. - (static)
                         Opinions vary on "Global" error checking in VB. - (mmoffitt)
         That's the technical term "set" - (FuManChu) - (4)
             Re: That's the technical term "set" - (acagle) - (3)
                 Yes, unfortunately. - (FuManChu)
                 Putting it in every procedure is good practice for VB. - (mmoffitt) - (1)
                     Dangitall. - (acagle)
         Update: (+edit) - (acagle) - (5)
             You're probably all over this, but... - (Steven A S) - (1)
                 Re: You're probably all over this, but... - (acagle)
             Where is the declaration exactly? And a few more q's. - (mmoffitt)
             Did you get this fixed? -NT - (mmoffitt) - (1)
                 Re: Did you get this fixed? - (acagle)

When will they realize that their stupid cult is not the only one?
98 ms