Results 1 to 1 of 1
  1. #1
    Join Date
    Dec 2002
    Columbus, GA

    Unanswered: Customize ODBC Error Output

    I am trying to figure out if there is a way to customize the ODBC errors that occur from SQL server inside of Microsoft Access. The sample of an ODBC Error below is simple to us designers but as most of you know, end users dont see things the way we do. All they see is the first line that says ODBC--call failed and they immediatly email us saying the database is broke.

    This is a NULL error, I know I can put validation in the form to prevent this but I need it for other errors too like DUPLICATE RECORD or PERMISSION DENIED, etc. My users never make it to the part of the error that says that.

    SAMPLE ODBC Error (current)
    ODBC--call failed.

    [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot Insert the value NULL into column 'Name', table 'Database.dbo.Employees'; column doe not allow nulls. INSERT fails. (#515)[Microsoft][ODBC SQL Server Driver][SQL Server] The Statement has been terminated. (#3621)

    SAMPLE ODBC Error (proposed)
    Cannot Insert the value NULL into column 'Name'

    Is there a way in either MSAssess or SQL Server to customize what is displaying in the error?
    Last edited by tsyscps; 10-25-05 at 09:37.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts