JMP application icons

[#1]

In all previous versions, each JMP file type had its own icon (eg *.jmp, *.jmpprj, jsl etc). This was quite handy when viewing the recent files pane in JMP since each was readily identifiable.  On installation of JMP 19, the software, for whatever reason, did not create a program association for jmp files  To correct that problem, I made the manual connection of a JMP data table file to the software.  Unfortunately, that now means that all JMP files have the same icon.  Is there some way to revert to the other icons for specific JMP file types?

[#2 · Accepted solution]

Windows PC?

go to preferences / Windows specific and click on Reset Associations.

[#3]

this issue often comes with another issue:

The function in the preference might fix the issue. If not, try this 2-step-approach:

https://community.jmp.com/t5/Discussions/New-instance-of-JMP-is-opened-each-time-a-new-file-is-opene... 

[#4]

I have gotten so used to the "bugged" icons that I don't really bother with them that much anymore but maybe these steps, JMP Note 639556 - Problem Note 52261: New instance of JMP® is opened each time a new file is opened , could help also with the icons as both might be related to file association issues. 

[#5]

Then maybe try the 2-step approach to fix it ;  )

[#6]

While I don't know the specifics of your situation one possibility is that you uninstalled an old version after installing JMP 19?  On Windows, file associations are stored in the registry with very loose ownership. Basically, the most recent application to register as the handler for ".jmp", for example, wins (gets to be associated).  In a related behavior, if you uninstall an app which had previously registered as the handler for a file type it can remove the registry information and unwittingly un-register a newer app.  ie. Install JMP 19 and then uninstall, say, JMP 17, the JMP 17 uninstall can remove JMP 19's registry information.  The Reset Associations button is an attempt to help here but it does require administration privileges because of the portion of the registry it affects.

So, this is not a solution but perhaps an explanation of "what happened?" for people who may have run into this situation.   The ideal sequence is to uninstall the old version before installing the new but obviously, that's not always possible.

And FWIW, a re-install ought to fix things up as well.