How to trap for ODBC errors

[Seth Schrock]

I have a database that its BE is SQL Server. Occasionally, I get ODBC errors, but they aren't going through my error trap. This is what I have right now:

On Error GoTo Error_Handler
 
'Procedure code here...
 
Exit_Procedure:
    Exit Sub
 
 
Error_Handler:
    Call ErrorMessage(Err.Number, Err.Description, "Module Name")
    Resume Exit_Procedure
    Resume
 

The sub that gets called is:

Public Sub ErrorMessage (ErrorNumber as Integer, ErrorDescription as string, _
                        Module as string, Optional CodeGroup as Integer = 0)
 
dim strMsg as string
 
strMsg = "Please contact the database administrator and provide the following information:" & _
         vbCrLf & vbCrLf & _
         "Error Number: " & ErrorNumber & VbCrLf & _
         "Description: " & ErrorDescription & VbCrLf & _
         "Module: " & Module & VbCrLf & _
         "Code Group: " & CodeGroup
 
msgbox strmsg, Buttons: = vbCritical, Title: = "My Application"

For some reason though, I'm still getting the normal ODBC error messages instead of my custom one. How do I get the error to go through my trap?

[ADezii]

You need to use the Errors collection to trap specific Open Database Connectivity (ODBC) Errors. Assuming you are using DAO:

Function TestODBCErr()
Dim errX As DAO.Error
On Error GoTo ODBCErrHandler
 
'Function Coding
 
Exit_function:
  Exit Function
 
ODBCErrHandler:
  If Errors.Count > 1 Then    'ODBC related
    For Each errX In DAO.Errors
      Debug.Print "ODBC Error"
      Debug.Print errX.Number
      Debug.Print errX.Description
    Next errX
  Else     'VBA related
    Debug.Print "VBA Error"
    Debug.Print Err.Number
    Debug.Print Err.Description
  End If
    Resume Exit_function
End Function

[Seth Schrock]

Thanks ADezii. I just realized that I have fixed the error that I was having so now I can't test for it. However, I think that if I have any problems that I will be able to figure them out so I'll go ahead and select your answer as best answer.