What will users think of all your programs if they give incorrect results? ..probably something wrong? You won’t be happy, and these guys certainly won’t think you’re bound to be a great programmer!

By reading the contents of this article, you will probably understand that temporary artifacts are bad, and besides, hiding them is a positive idea. As you gain a little more experience, you realize that this is clearly not the case, and mistakes would actually be a blessing – they either tell you that you did something wrong (and this thought is wrong), or something is wrong. is a proprietary program independent of administration (but you haven’t written much code).

Either way, VB tries to tell you what the dilemma is (leaving the routine aside), you keep deciding to stick your fingers in your ears and yell “I never listen!”

When and how to use it?
There are two types of situations, especially when it’s appropriate:

1. Don’t worry about the code being executed correctly because it can’t harm a person. You are hope!
2. Are you waiting?You’re getting an error in a certain part of the model, but due to the size/structure and the procedure (or what that distinctive piece of code does) it’s important to handle the error where it occurred (by checking Err.Number right after) than in a different error handler for an existing routine.

If you regularly use the first type (more than 10% of your preferred error handling), I’m worried!

The use of the first type is correct and generally “correct” use. Just be sure to resort to frequent error handling after this rule (or let the routine check for all errors), otherwise you’ll run into the above problems again.

In general, you should use the perfect bug as the treatment described in this separate article. Treaty