JSL: Open succeeds in JMP 16.1.0, but fails in Jmp 17.0.0

[#1]

Hi All,

I have a strange issue where an Open will run successfully in JMP 16.1.0, but will fail when run in JMP 17.0.0. I am running the same .jsl file in both cases.

The code below fails when run on JMP 17.0.0. The error occurs on the Open, with a log message of "Cannot open table in access or evaluation of 'Open' , Open/*###*/(dt2, Worksheets( "PD cPCR" ), Table Contains Column Headers( 1 ),

invisible)"

The file being selected is an Excel file, and the worksheet being selected has 21,000+ rows. Trying some trial and error, I'm able to open the file if I delete all rows except for a few. Leaving in 1000 rows still results in the error. 

Does anyone have ideas for further troubleshooting? Unfortunately, I can't share the file here without significant and time-consuming scrubbing/anonymization.

dt2 = pick file ("Pick cPCR reference file", "C:\JMP\");
dt2 = Open(dt2,
        Worksheets("PD cPCR"),
        Table Contains Column Headers( 1 ),
        invisible
        );

[#2]

Can you open the file fine using JMP's File -> Open menu in both JMP versions?

[#3]

Yes -- I'm able to open the file successfully through File -> Open in both JMP 16.1 and JMP 17.

[#4]

Even though I can open the file via File -> Open, I want to open it using JSL (to avoid involving manual operations during script execution). @jthi or anyone else, any ideas for further troubleshooting? 

[#5]

Please inspect the Source table script produced by both versions of JMP when you open the file. Are there any differences?

Example:

//JMP 16.2.0
    Open(
    "$DESKTOP/test.csv",
    columns(
        New Column( "Col 1", Character, "Nominal" ),
        New Column( "Col 2", Character, "Nominal" )
    ),
    Import Settings(
        End Of Line( CRLF, CR, LF ),
        End Of Field( Comma, CSV( 1 ) ),
        Strip Quotes( 0 ),
        Use Apostrophe as Quotation Mark( 0 ),
        Use Regional Settings( 0 ),
        Scan Whole File( 1 ),
        Treat empty columns as numeric( 0 ),
        CompressNumericColumns( 0 ),
        CompressCharacterColumns( 0 ),
        CompressAllowListCheck( 0 ),
        Labels( 1 ),
        Column Names Start( 1 ),
        Data Starts( 2 ),
        Lines To Read( "All" ),
        Year Rule( "20xx" )
    )
)

//JMP 17.0.0
Open(
    "$DESKTOP/test.csv",
    columns(
        New Column( "Col 1", Character, "Nominal" ),
        New Column( "Col 2", Character, "Nominal" )
    ),
    Import Settings(
        End Of Line( CRLF, CR, LF ),
        End Of Field( Comma, CSV( 1 ) ),
        Strip Quotes( 0 ),
        Use Apostrophe as Quotation Mark( 0 ),
        Use Regional Settings( 0 ),
        Scan Whole File( 0 ),
        Treat empty columns as numeric( 0 ),
        CompressNumericColumns( 0 ),
        CompressCharacterColumns( 0 ),
        CompressAllowListCheck( 0 ),
        Labels( 1 ),
        Column Names Start( 1 ),
        First Named Column( 1 ),
        Data Starts( 2 ),
        Lines To Read( "All" ),
        Year Rule( "20xx" )
    )
)

[#6 · Accepted solution]

The tech support link at the bottom of this page will get you help from the JMP team. And likely get the problem properly fixed in a future release.

[#7]

As the files can be opened with JMP properly, I agree with @Craige_Hales about contacting support. They will be most likely help you and if you get solution please post it here. This way everyone else can learn what could be the issue if they were to face similar problems.