I/O error after updating to new JMP version (JMP 18 windows)

[#1]

Hey everyone,

I had been running script every day for years and then we updated to JMP 18 and it is no longer working as intended.

It pulls data and appends it to a table but it used to let me run it multiple times and keep appending to the same table. Now it is opening a new table each time. Additionally, it will not save the table. It says it is not in write mode and instead of saving it to the network location that it is opening it from, it is trying to save to "C:\me\desktop\L:\yadda\yadda"

I tried updating some file locations under preferences but this hasn't helped. 

Does anyone have any insight into these problems?

[#2]

Partial answer: when JMP opens a table, it tries to get a write lock to prevent another user from also updating the file on disk (because one of the two users would lose their changes.) The lock is released when the table is closed. I think you'll see the "locked" in italics in the left panel when JMP can't get the lock.

It sounds like this is happening within a single instance of JMP. I'm not sure why JMP wouldn't still see the network disk file as the same and use the same already open data table.

You might do an experiment with "unc" names, something like

\\server\path\xxx.jmp rather than the drive mapping to L: and see how that changes things.

And what was the previous version of JMP that worked?

edit: make the unc name a little more correct

[#3]

also "C:\me\desktop\L: ..." is a really odd thing; the drive letter L: does not belong inside a path after C: 

[#4]

The previous version was JMP 15. And yes, the idea of JMP deciding to nest L instead of C is baffling to me.

[#5]

If you can share a small example that produces the problem, someone might be able to spot something. You might also want to start with the support team (tab at top of page.)