I have an Access 97 application that uses tables linked through ODBC to an Oracle back end. I'm finding that it returns the same error (basically a generic ODBC connection error) whether the user puts in the wrong user name or password, or if the DSN doesn't exist on the machine.

I've been able to adapt code to create the DSN programatically, but I need to be able to trap for the specific ODBC connection error.