I have the pleasure of working with a distinctly flaky odbc connection. It tends to fail on startup but it also fails randomnly throughout my time operating on the database.
So I have two questions:
How can I trap any and every ODBC connection failure message and deliver a custom error message to the user, so they won't have the bejesus scared out of them?
And is there anything that can be done to improve the odbc connection to ensure that it stays open (we're operating off of a lan and the odbc connection is to a PostgreSQL database made by one of the it guys)?
So I have two questions:
How can I trap any and every ODBC connection failure message and deliver a custom error message to the user, so they won't have the bejesus scared out of them?
And is there anything that can be done to improve the odbc connection to ensure that it stays open (we're operating off of a lan and the odbc connection is to a PostgreSQL database made by one of the it guys)?
