nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

886257_en-US

liliconcom

Cleaner failure / messaging for Database Driver issues

What inspired this wish list request? JMP 18 and 19EA were crashing when attempting to connect ODBC to Snowflake (see case number below). Very little in any logs / tracing explained the error. It turns out my snowflake driver was older. 1) I didn't know there were new drivers availeable and 2) I didn't know that JMP wouldn't work with the older driver.

What is the improvement you would like to see? I would like a cleaner error -- not a fatal crash -- and some form of messaging to indicate to the user of the issue or possible fixes.

Why is this idea important? Any solvable error that results in a fatal crash of JMP is important to fix

Ideally, the fix would be clean enough to recognize driver versions and note which is the minmum to use. I realize that may be tough given the plethora of drivers / versions out there.

So the miniumum wish would be a non-fatal crash of something going wrong and a suggested check of driver version updates.

Data Access

Re: Cleaner failure / messaging for Database Driver issues - Status changed to: Acknowledged

Thanks for posting this suggestion @nathan-clark . We're working on handling uncaught errors (crashes) more gracefully. If you do encounter a crash, please report to support@jmp.com.

Re: Cleaner failure / messaging for Database Driver issues

Thanks @mia_stephens! I had originally brought this to jmp support, and the end was recommended the wish list so that's what I've done. In the end, the crash was "my fault" 'cause a driver wasn't updated, so things are working now, but I appreciate the teams working to make crashing cleaner wherever possible!