Trap ODBC errors?

Trap ODBC errors?

Post by Simon Clar » Wed, 10 Nov 1999 04:00:00

How can I trap the "Driver is probably out of resources..." error which I
get when a deadlock appears on my server?

I have a bunch of VFP6 clients in which I placed an error trap, but it never
caught this ODBC error...

Help please!!


Member, WorldWide SQL Server User's Group (


1. Trapping ODBC Errors

Hello all:
I'm in the process of build some forms in VB to display ad hoc queries
in a grid.  I am using Oracle 7.0 and ODBC as the storage and connection
medium.  If the user enters an invalid query, I can trap the error from
ODBC, which is #3146, for all errors.   Is it possible to get a
more detailed error number or message.  I thought about using ODBC API
but how would I get the error without logging in, creating environment
and statement handles, etc.   Am I attacking this problem the wrong way?


2. ActiveX Licenses

3. Trapping ODBC error codes

4. Problem with connecting to sqlserver

5. Trapping ODBC Errors in VB 4.0 - HOW ???

6. ODBC and NT4.0 and Visiual C++ 5.0 and MS-Office 97

7. Trapping ODBC Errors

8. How can I activate a trace (at the server level) without cycling SQL server

9. HELP Unable to trap ODBC errors

10. Error Trapping ODBC Error 3021 'Record Not Found'

11. SQL Server & Access 97: Cannot trap ODBC Errors with Form OnError event