cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Don’t miss your chance to experience Discovery Summit Europe at our best available rate! Early bird registration through 31 Oct.
  • Graph Builder Toolbar streamlines interactive graphing. Creates shortcuts on Report and GraphBuilder Helpers toolbars. Download and install the extension.
  • JMP will suspend normal business operations for our Rest and Recharge Day on Friday, October 2, 2026.
    Regular business hours will resume on Monday, October 5, 2026.

Discussions

Solve problems, and share tips and tricks with other JMP users.
Choose Language Hide Translation Bar
hogi
Level XIII

Oops - I lost my data ...

Remember, you must not ....

  1. create a virtual link with a wrong table reference (fixed <= v18.2.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]

12 REPLIES 12
HaltsMaulwurf
Level II

Re: How to make a data table non-accessible?

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

 

jthi
Super User

Re: How to make a data table non-accessible?

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

-Jarmo
hogi
Level XIII

Re: Oops - I lost my data ...

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:

hogi_0-1734610373533.png

same issue with linked subset tables?


fixed in JMP18.2.2?

Recommended Articles