topic Re: I/O error when close a data table in Discussions

I/O error when close a data table

kanpiner — Tue, 17 Mar 2020 17:38:07 GMT

Hello,

Recently I just installed JMP 15. Whenever I attempted to close a non-empty data table, the log will pop up with the following error message:

"Save changes to the JMP Data Table Untitled 25?

I/O problem.

Untitled 25.jmp
Unable to open in ReadWrite mode.
The system cannot find the file specified."

The table has nothing special. I just created a new one and type in random words in the cols;

I have tried reinstall jmp, no help; tried to change directory folders I am sure to have access with, no help;

This problem is really annoying and not sure how to get rid of it.

Any suggestions will be appreciated!

Re: I/O error when close a data table

stan_koprowski — Tue, 17 Mar 2020 18:01:35 GMT

Hi @kanpiner ,

I would contact technical support (support@jmp.com).

They can best help you come to a resolution.

cheers,

Stan

Re: I/O error when close a data table

pmroz — Wed, 18 Mar 2020 14:50:35 GMT

Have you tried updating to JMP 15.1?

Re: I/O error when close a data table

Zahti — Wed, 20 May 2020 23:26:00 GMT

In JMP 15 there are some extra parameters for the Close(); function that were not required in JMP 14. I just found this out today as well and it is quite frustrating... broke all my scripts :)

JMP 14 syntax:

Close( "Table1" );

JMP 15 syntax:

Close( "Table1", NoSave );

Hopefully this helps!

Re: I/O error when close a data table

pmroz — Thu, 21 May 2020 11:52:10 GMT

The nosave parameter has been part of the close() function since at least JMP 11, if not earlier. I tried creating a table and then calling close(dt) in JMP 14 and 15, and the table closed no problem. Interesting though - the table was automatically saved to my desktop.

As a rule I call close() with the nosave argument if I've got some temporary work tables.

How did this break your scripts?

Re: I/O error when close a data table

rcookie — Thu, 02 Mar 2023 12:50:57 GMT

Had the same issue, adding the nosave argument fixed it (JMP15).