Remember, you must not .... * create a virtual link with a wrong table reference (fixed <= v18.2.2) * create a summary table with a compact column (fixed <= v18.2.2) It makes your data table non-accessible! [More Topic Containers like this]

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oops - I lost my data ...

hogi

Remember, you must not ....

create a virtual link with a wrong table reference (fixed <= v18.2.2)
create a summary table with a compact column (fixed <= v18.2.2)

It makes your data table non-accessible!

[More Topic Containers like this]

Accepted answers

All comments

hogi

option 1):
add a Link with a non-resolved reference:

  Names Default to Here(1);

dt =  Open( "$SAMPLE_DATA/Big Class.jmp" );

dt << new column("Conan the Destroyer",Set Property("Link Reference", {Reference Table(link_path), Options("Use Linked Column Name", "Auto Open")}));

dt << save("$TEMP/test.jmp");
close(dt, noSave);

open("$TEMP/test.jmp");

fixed in JMP18.2.2?

jthi

In what sense non-accessible?

hogi

In the sense of "dead".

hogi

The good thing:
JMP stores the Table reference in plain text ...

By deleting the ", Auto Open" one can revive the file:

JMP will show a warning message:

and skip the details of the erroneous column.

txnelson

What is the purpose of this thread?

jthi

Why would you want to make your data non-accessible in such a way that it is basically corrupted?

Dahlia_Watkins

I believe understand the problem after speaking with another colleague.

The issue here is the JMP user interface will not allow one to save a table, with Auto Open selected, while an invalid Link Reference path exists. The JMP UI will save the table but will set the Auto Open option. So the table can be opened or recovered.

In JSL however, it is permitted. The table is saved with Auto Open and an invalid Link Reference. This prevents JMP from opening the table. The JMP UI has some sort of safety check in place that is not built into JSL.

I've reported this issue so it can be addressed in a future release.

Best!

hogi

#1:
Hi @Dahlia_Watkins , thank you for digging deeper and triggering a bugfix for a future release : )

[TS - 00177463]

HaltsMaulwurf

Thanks hogi,
I could rescue a few of my datasets with your solution! Highly appreciated

hogi

option 2) create a summary table

- with a link to the main table (default)

- with a compact column

dt = New Table( "input",
	Add Rows( 3 ),
	New Column( "ID",
		Character,
		"Nominal",
		Set Values( {"A_1", "A_2", "A_3"} ),
		Compact() // <- disable to remove the bug
	)
);

dt sum = dt << Summary(	Group( :ID ),
//Link to original data table( 0 ) // <- uncomment to disable the bug
);

fn = "$temp\bug" || Char(random integer(10000))||".jmp";
dtsum  << Save( fn );
Close( dt sum, NoSave );
Try(open(fn), Caption("sorry, the file is damaged"));

When you try to open the file manually, JMP will display an error message:

same issue with linked subset tables?

fixed in JMP18.2.2?