New instance of JMP® is opened each time a new file is opened

[#1]

Hi everyone,

I've searched around and found some solutions to the problem that I am having, but none of them have seem to worked for me, so I thought I would just ask again to see if anyone might have some additional insight.

I help train colleagues at our company in using JMP and one problem that we regularly encounter is that if someone opens a file from Windows Explorer while they already had another JMP file open, the new file opens in an entirely different instance of JMP, thus cluttering up the taskbar and making it impossible to carry out tasks between the two files (like merging the two tables, etc). Obviously, once we realize that is the problem, we save the file, shut down the second instance of JMP, and reopen the file in the original instance, but this is a problem that frustrates many of us, so I thought instead of being frustrated, I would ask to see if anyone had a solution.

I have tried the solutions discussed in https://community.jmp.com/t5/JMP-Knowledge-Base/Problem-Note-52261-New-instance-of-JMP-is-opened-eac... but although it perfectly describes the problem, the solutions don't seem to help the situation. I have also tried what I have permission to do [based on my operating system permissions], but likewise, I have not been able to solve the problem.

Thanks in advance for any insight!

[#2]

Thank you Patrick, strange as it seems, this is the solution that worked for me!

[#3]

Note on this solution:  It didn't work at first but when I repaired the installation of JMP and then tried the notepad trick it work!

[#4]

it magically worked to me. thx!

[#5]

Well, I had the same problem on my Windows computer!

This one did not help:

Then I tried:

... with success.

I had the issue with another user account - so I tried (1) - and it didn't work ?!?
So, I FIRST went to the preferences and applied

and THEN I tried (1)

... and it worked.

The proof of success: If the icons look like this

... and not like this: 

check on your own and give feedback ...
By the way - no need to enable this option:

[#6]

Yes it works! I had to repeat step (1) not only for .jmp, but for .jrn and .jmplow files too. Now each file has its own icon and opens in the same current JMP 19 instance.

[#7]

Thanks Hogi, this worked for me. I installed 19 but wanted to keep an older version default for now.  I had previously clicked 'reset file associations...' in preferences but that didn't fix it. Then I did what you have in step 1 and it worked. So far i only did it for jmp and jsl files and that's fine for me for now.

[#8]

As we have this issue very often:

1)  

2) Follow @PatrickGiuliano 's steps: 
https://community.jmp.com/t5/Discussions/New-instance-of-JMP-is-opened-each-time-a-new-file-is-opene... 
... for every affected file type (!!)

@PatrickGiuliano , is this the only solution?

[#9]

@hogi yes as far as I understand! thanks for resharing this approach -- I do find it very effective when "Reset Associations" doesn't do the trick.

Only other thing I would add is -- if it's not already obvious to users -- you can open a JMP session, use the Home Window as your "home base" (no need to rely on the Projects framework, just use the file hierarchy to understand where you are and what you have open), and drag and drop your JMP files from their applicable location into the home window itself. This will ensure that they open in the session that you want them to. Also use File > Open from within the JMP session (from the Home Window) and that will help you organize your work also. I do sometimes intentionally keep multiple sessions of JMP open (maybe two or three) to track several different work-flows. Also if I'm doing something more mission critical, that helps because if I'm clicking around haphazardly in one session, I'm "Ok" with that session potentially crashing, while I might be more deliberate in another session where I have a larger work-flow oriented around a particular project with a particular analysis direction in mind.  I hope it goes without saying here that JMP should never crash -- we are always working hard to improve that. 

[#10]

@althompsonphd The note reference in your original post is for Windows only.  We generally do not see this behavior from Mac OS.  Since Mac OS is driven by configuration files and not a Registry database like Windows, I would recommend deleting the related JMP configuration files.  JMP will rebuild them on the next launch.  However, you will need to supply the JMP license file or serial number again.

The steps below come from this JMP Note 678317

Remove JMP User Customization Data

1) From Finder, select Go > Go to Folder…

2) Type ~/Library and hit Enter

3) In the user’s Folder, open the Application Support folder

4) Select the JMP folder and drag it to Trash

(You might have to provide your password to complete the action)

5) Navigate back to ~/Library

6) Open the Preferences folder

7) Find all the “com.sas.jmp” files and drag them to Trash. 

There will be at least com.sas.jmp.plist and maybe more than one.

If the step above do not resolve your issue, please contact support@jmp.com to open a Technical Support case to further investigate this issue.