Do's and Don'ts So Others Won't

Originally Posted by romperstomper

You mean you don't use error handling blocks, you just use On Error Resume Next?

Correct. In effect, error handling blocks are in line with the code. I will use Exit Sub in the block after setting appropraite error flags, if necessary.

I know this is a style thing. I find it easier to assure myself that I have handed error conditions by leaving the hanlding block near the error.

If VBA had try...catch like other languages, I would prefer it. On Error Resume Next the closest I can get.

Originally Posted by blane245

If VBA had try...catch like other languages, I would prefer it. On Error Resume Next the closest I can get.

I would have said that on error goto label was closer to Try...Catch, but hey, it's your code.

Of course that assumes you can predict every single error...

Originally Posted by romperstomper

I would have said that on error goto label was closer to Try...Catch, but hey, it's your code.

Of course that assumes you can predict every single error...

You are right about goto label being close to try...catch. You got me on that one. I think the goto label method is definately a good way to protect code for any type of unforseen error, though a bit weak in knowing what to do when one of those unforseen errors occur. In general, doing exception handling is like writing a second program inside on the original one.

Error prediction is an essential part of robust coding. If you are trying to protect against hardware as well as software faults, then there may no other way than to use on error goto label. But in the VBA environment, I am not sure your code will get control on those types of errors. For example, if you have a read failure on a disk drive, will VBA let your code get control of that, or will VBA or Windows trap that error and forget about you.