The short answer is no to all your questions, because the Form Error sub is *not* where the error occurs.  In Richard's example, if the user makes an erroneous entry, the error should normally occur in the *AfterUpdate* event.  But you have no way of knowing that, because you are not in the AfterUpdate event.  

The Form Error event only gives you the error code, but not the exact error message (which is contextual, and may be different even for the same error code), nor the line of code that caused the error.  Only the "On Error" statement can give you that info.  

The only way to get the complete info about the error is to put the error handling into each and every procedure in your database, as I said in the other thread ( https://599cd.com/blog/display-comment.asp?CommentID=93969 ).  

Also, an error handler is mainly for trapping errors you don't know about in advance.  If you know what errors would occur (e.g. if you know the user may enter the wrong date), it is better to just *prevent* the error from occurring (with If-Then statements and/or the BeforeUpdate event, as Richard mentions in the video) rather than invoking an error handler.

Thirdly, errors don't always occur in forms.  They may occur in standalone VBA modules, in which case the Form Error event would be useless.

Fourthly, VBA code often involves "cascading events:" procedure A calls proc B, which calls proc C, D, etc.  The only way to pinpoint where an error occurs exactly is to put error handling in A, B, C, etc.  There is no way to get around that.  As I said before, there is no "global" handling of this.  And this is not a shortcoming of Access.  Many other environments are like this too.  

Creating a good error-handling feature is a *prime* task, one that is not always done well even in commercial products.  That's why sometimes we see apps (such as Windows itself) go into an unusable state that requires a restart.

Thank you, very useful information. So this kind of error capturing is for indexed fields with no duplicates that way it tells the person that they have duplicated information. This also could be used as a for wrong format and stuff like that.

I rarely used the Form Error event in my old job because it doesn't give enough info of the errors; and for the errors it does catch, there is always a way to prevent the error in the first place.