JMP compresses imported images. But at the moment, JMP stores every image separately of the the other images.
So, when the user imports the same image multiple times - the memory consumption increases with every "new" image.
An easy solution: follow an approach which was was presented by @julian on Discovery Summit Europe 2025
https://community.jmp.com/t5/Abstracts/Scaling-Innovation-Integrating-Data-Science-into-Engineering/... :
Store the images in a separate table - and use a virtual link with an index column.
The cool trick:
After setting up the virtual link, Julian un-hides the column and drags it "into" the main table to make it nicely visible.
Unfortunately, after saving, closing and opening the data table, the virtual column is move to the end of the main table (I guess along the idea: the linked table might have changed, so better reset the configuration with every new start).
- Is there a way to position the column with the images permanently between columns of the main table?
- I tried to copy the content via a formula column. but the behavior is strange:
when I edit an entry of the index column, it's just the virtual column that gets updated - the formula column is lazy and keeps it's original content. [when I add a new row, the content of the formula column gets updated.]
names default to here(1);
Open( "$SAMPLE_DATA/Big Class Families.jmp" );
Open( "$SAMPLE_DATA/Big Class.jmp" );
Data Table( "Big Class Families" ) << Select Where( :name == "ROBERT" ) <<
Delete Rows;
Data Table( "Big Class Families" ):name << Set Property( "Link ID", 1 );
Data Table( "Big Class" ):name << Set Property(
"Link Reference",
Reference Table( "Big Class Families.jmp" )
);
Data Table( "Big Class" ) << New Column( "1:1 copy",
Expression,
"None",
Formula( :"picture[name]"n )
) << Run Formulas;
Data Table( "Big Class" ) << Move Selected Columns( {:"1:1 copy"n}, To First );
