Fix JMP Bug: ODBC-Error not forwarded to user
Fix JMP Bug: ODBC-Error not forwarded to user
What inspired this wish list request? We have been struggling with incomplete datasets, i.e. from different query executions we got different number of rows from database using "new sql query" with ODBC-DSN. This occurs because the query connection runs in timeout during data fetch, and JMP did not forward the error and inform user about this.
What is the improvement you would like to see? I need JMP to inform user about the ODBC error, that the user knows that there is an issue and she/he can fix it.
Why is this idea important? Because with this behaviour the user looses the confidence that data acquisition by JMP works correctly and dataset is incomplete. It is just a bug fix.
As a workaround I was told to configure the timeout in the ODBC-settings, but this will work only, when user is aware of the issue. Without JMP informing him about the issue, he will probably not be aware of it. Even when he is aware of the issue, the next query can take longer, and he again may run into the same issue. So he needs to pull the data several times to know if there is an issue. That's something that I don't like.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.