Application Not Found error when trying to open a data table in JSL

[#1]

I'm am trying to open a data table using the following code:

Names Default To Here(1);

dt1 = Open( "f3uel_airborne_2020_data");
dt2 = Open( "peaks_data_431");

When I run this, I get an Application Not Found error in the log and it fails to open.

Does anyone have any idea what may be going on here? I'm using JMP19 on a Mac.

[#2]

Guessing, no mac here, I think the file JMP is finding might not be a JMP data table. (On win, JMP tables have the .jmp extension.) JMP might be finding a .excel file but no excel application installed. 

[#3]

Well… I thought that too. I checked the file type and it is a JMP data table. If I double click on it, it opens in JMP.

[#4]

Strange, I am not a MAC user either and I will probably suggest something you have already thought but did you try to include full path in the quotes " "

[#5]

I did put the entire path name in quotes and still got an error. I'm totally stumped.

[#6]

Let the support team have a go at it (tab at top of screen). Let us know what the answer is, seems really odd.

[#7]

Mac question - what OS are you running?  Did you take the new update to Tahoe(26), or are you still running Sequoia(18.7)?

Also - once you double-click and open the file, does it then work and open with the JSL?

And does this happen with all data tables you open, or is it only with the Underscores in the file names?

[#8]

One other thing to check @scott1588      if you go to Mac Settings -> Privacy & Security -> Files & Folders, you'll see a list of apps that have permissions to access certain folders... you may need to make sure your JMP 19 has access to a  given folder where your table is located. File > Open also should allow you to navigate and pick a table to open in JMP - does that work?

[#9]

Thanks for these suggestions, Mandy.

Well... I just shut everything down and re-booted my computer. I changed nothing in the code. Now it works.

This was very strange. I still have no idea what was going on but at least for now it seems to be fixed.

Thank you all again for the awesome support this forum provides. It's one of the main reasons I use JMP.