Oops - I lost my data ...

[#1]

take care that you don't:

1. create a virtual link with a wrong table reference
2. create a summary table with a compact column 

[#2]

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

Names Default to Here(1);

testMode= 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");  

[#3]

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!

[#4]

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

[TS - 00177463]

[#5]

In what sense non-accessible?

[#6]

In the sense of "dead".

[#7]

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.

[#8]

What is the purpose of this thread?

[#9]

---

@txnelson wrote:

What is the purpose of this thread?

---

mainly: Help people save their work.

Besides that:
a) Documentation: Things you should NOT (!!) do with your data table.

b) Motivation:
@ colleagues - please invest 30 minutes to understand the beauty of Eval/Eval Expr/Expr
(the basics: # 62, some examples: #66)  ---  it will save you from lost data like this one.

c) preventive action:

-> I will add a check + warning functionality to the  button ...
if a variable is defined in the script - and the variable shows up in a message (<<  ...) ... show a WARNING !

[#10]

---

@hogi wrote:
a check + warning functionality  ...

---