User Community
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • New to JMP? Join us Sept. 23-24 for the Early User Edition of Discovery Summit, tailor-made for new users. Register now for free!
  • Your voice matters! Tell us how you prefer to receive JMP updates, so we can tailor our communication to your needs. Take short survey.
  • See how to access JMP Marketplace - and - find, create & share add-ins to extend your JMP. Watch video.

Discussions

Solve problems, and share tips and tricks with other JMP users.
Choose Language Hide Translation Bar
DMerchen
DMerchen
Level II

Skipping Values in Query but Seen in Preview

Created: Sep 10, 2021 12:22 PM  |  Last Modified: Jun 10, 2023 4:36 PM (2548 views)

I am pulling data from an SQL database. In the updated preview it looks good, but when I run the query, not all of the values fill in properly. Any idea what is happening with this?

DMerchen_0-1631290799771.png

Thanks,

Dave

DMerchen
0 Kudos
3 REPLIES 3
Phil_Kay
Staff Phil_Kay
Staff

Re: Skipping Values in Query but Seen in Preview

Sep 14, 2021 04:41 AM (2521 views)  |  Posted in reply to message from DMerchen 09-10-2021

No, sorry! I haven't seen anything like this before. And without being able to investigate your data source and connection it is very difficult to help. I think this might be a better question for technical support (email: [email protected]).

0 Kudos
DMerchen
DMerchen
Level II

Re: Skipping Values in Query but Seen in Preview

Sep 14, 2021 04:25 PM (2513 views)  |  Posted in reply to message from Phil_Kay 09-14-2021

I will respond to tech support. They have already reached out. If I get a solution I will be sure and post it here.

DMerchen
DMerchen
DMerchen
Level II

Re: Skipping Values in Query but Seen in Preview

Dec 7, 2021 07:02 PM (2490 views)  |  Posted in reply to message from DMerchen 09-14-2021

It was an older MySQL driver issue. Now having to use 2 drivers for MySQL. One for JMP and one for the internal database. It works!

 

The newer driver for JMP fixed the issue I was seeing. I went through several drivers until I finally got to one that worked. JMP also doesn't like if the driver is too new, so there seems to be a sweet spot with MySQL 5.2.

DMerchen
0 Kudos

Recommended Articles