Error Handling

[trb5016]

So I have a (I think) fairly large database with lots of vba code. I want to go in and add error handling to all of it (I've got like 6000ish lines of code)

Should every single procedure have an error handler?

Like, if there's a command button that just has the line
DoCmd.Openform "Form1"



does that need all the error handler code in it?

I mean, I can't foresee that code not working, but I'm sure it's possible. On the other hand that's going to be adding a lot of code...


Opinions?

[Rawb]

Unfortunately, every function that can throw an error will need it's own error handling. Generally speaking, that means any function running a DoCmd Event or that accesses a Recordset.

As for the functions where you're just saving Records or opening or closing Forms, unfortunately you will need error handling in there. I've run into several instances when I've gotten a "Save changes" prompt (or similar) and had to hit Cancel. And, technically, canceling throws an error. . .

Error handling - even in simple functions like those mentioned above - is especially important when you have users using the Access Runtime. The Runtime crashes on every unhandled error it comes across! This means that, if someone tries to close a Form using a button, gets a prompt, and hits Cancel. . . If you don't have error handling in that function, the Runtime's going to crash.

[trb5016]

Yea, I figured this was going to be the case. I wish I had done this as I went along but I didn't even know how when I started making this haha.

Thanks for the good advice.

*sigh* it's my own fault lol