I have a problem with the return type ODBCError. My point is that when you run ODBC.DSN(...), you have either a DSN type or a ODBCError in the case something went wrong. In that last case, you just have a string. It would be nice to know which error cause the sql_error. Is there a way
to have more information about the error for example to use in a try catch statement (without having to parse the string...) ? Is it possible to add the error type from the sql to get more information of what went wrong ?
Hi,
I have a problem with the return type ODBCError. My point is that when you run ODBC.DSN(...), you have either a DSN type or a ODBCError in the case something went wrong. In that last case, you just have a string. It would be nice to know which error cause the sql_error. Is there a way to have more information about the error for example to use in a try catch statement (without having to parse the string...) ? Is it possible to add the error type from the sql to get more information of what went wrong ?
Thanks a lot,
Erwan