Feedback by UserVoice

I suggest you ...

← Access (Desktop Application)

ODBC errors need to return more information error 3146 does not provide enough detail

Perhaps an error.description2 property which we can reference which stores the error returned from SQL about the true problem. Right now it is very difficult to trouble shoot.

Thanks.

11 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

5 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Mark Jaskula commented  ·   ·  Flag as inappropriate

    I can confirm Anders comment, it's a fantastic titbit particularly when you get referential integrity errors and want to know the culprit easily.

  • B. Clothier commented  ·   ·  Flag as inappropriate

    FYI - there is also this known issue that is a *big* PITA... From an old KB article..

    http://helpdoc-online.com/Microsoft_Knowledge_Base_October_2001_Access_en/ACC_Can_t_Trap_Specific_ODBC_Errors_OnOpen_Property.php

    (note that the title is misnamed - it says "OnOpen" but it's actually referring to "OnError".

    Addressing this pain point would go a long way toward making it easier to handle ODBC errors.

  • Anders Ebro (TheSmileyCoder) commented  ·   ·  Flag as inappropriate

    Hi John.
    Not commonly known, there is a Errors collection. Now I only know of one case where the Errors collection contains more than 1 error, and that is for ODBC errors. So my error handler takes special care of that situtation with the below code:
    'Special case for ODBC errors.
    If Err.Number = 3146 Then
    Dim i As Integer
    For i = 0 To Errors.Count - 1
    strErrDescription = strErrDescription & vbNewLine & "ODBC:" & Errors(i).Number & " - " & Errors(i).Description
    Next
    End If

    That usually gives enough information to track down the underlying issue just fine.

    I hope that helps.

Access (Desktop Application): External Data Connectivity

Categories

Feedback and Knowledge Base

(thinking…)