After moving to a new computer from HP the JSL scripts produced with a DELL computer do not work anymore. Both machines work with WIN10. The JMP software freezes after script start.
I'am looking for ideas what needs to be checked.
Thank you.
"That's certainly a bigger difference but doesn't seem like a size that should really be cause for concern."
Dear Julien,
FYI - Beginning of this year we started with a new database (3MB) and archived the old database (895MB), that could only be imported with the old DELL computers. Immediately with the change to the smaller database the JSL script was working as well on the new HP computers. -> database size matters
Regards,
Petra
Hi @PS_Ato,
This sounds really frustrating! There's really no reason a jmp script should have trouble on one computer and not another. As a first question, are you running the identical version of JMP, and what version is that? I assume the same major version, but are both machines running the latest minor update as well? Did you have custom preferences set for jmp on the first computer? If so, have you transferred your jmp preferences from your other computer? Importantly, can you give us a sense of what the script is doing? The more details you can provide the better. Some specifics: do you have any references in the script to files/directories? If so, are you sure those files/directories are in the same locations? Are you connecting to any databases in your script? A failure in any of these should not cause a crash, but perhaps there is something unique here that creates some kind of issue.
@jules
Hi Julian,thanks for looking into this.It is JMP verison 14 on both computers. The computers are connected to the identical network. The file location is the same. It is independent of the user logged to our system.Exemplarily, I checked the jmp prefrences: they are the same.
I checked other JSL scripts. One script is working, that imports xls data and does some additional operations and graphs.
The kind of JSL script that do not work refer to databases and files, e.g.
// Opening of database for tbox_value ("inspection lot") If( tbox_value != "", sql = Eval Insert( "SELECT TRBallShearHSBTTSF.Sample, Test, DateSave, ResGrams AS [Shear Strength (g)], Grade AS [Fracture Mode], ResmJoules AS [Total Energy (mJ)], PrePeakEnergy AS [PrePeakEnergy (mJ)], PostPeakEnergy AS [PostPeakEnergy (mJ)], Speed*0.001 AS [Speed (m/s)], TestTime*1000 AS [TestTime (ms)], User1 AS [Inspection Lot], User2 AS [Customer], User3 AS [Surface Finish], User4 AS [Leg], User5 AS [Aging], User6 AS [Test Substrate], User7 AS [Solder Paste / Flux], User8 AS [Solder Balls], User9 AS [Reflow Profile], User10 AS [Delay Time], Operator, FDTData FROM TRBallShearHSBTTSF INNER JOIN SSBallShearHSBTTSF ON TRBallShearHSBTTSF.Sample = SSBallShearHSBTTSF.Sample WHERE User1 LIKE '%^tbox_value^%'"); ); dsn_string = "DBQ=X:\- Assembly\Dage4000\Dage4000HS.mdb;DefaultDir=X:\- Assembly\Dage4000;Driver={Driver do Microsoft Access (*.mdb)};DriverId=281;FIL=MS Access;FILEDSN=X:\- Assembly\Dage4000\Dage4000HS.mdb.dsn;MaxBufferSize=2048;MaxScanRows=8;PageTimeout=5;SafeTransactions=0;Threads=3;UID=admin;UserCommitSync=Yes;"; dt = Open Database(dsn_string, sql, "HSS-Dage 4000");
The script starts promissing with opening a dialog box. But after clicking "okay" - next would be opening the database - it freezes.
I assume both computers have X: mapped to the same network location, and are logged into that remote server with the same credentials (and thus have the same access permissions) so it's not an issue with jmp accessing X:\- Assembly\... Assuming no problems there, I think perhaps it has something to do with that database connection. If you go to File > Database > Open Table on both machines, do you have the same database connections listed as available? I'm wondering if perhaps the two systems aren't configured in the same way, either in jmp, or in your ODBC Data Source Administrator. Full disclosure, database configuration isn't a specialty of mine so it'll be up to you to tell if something there is configured differently in a way that could matter.
Hi Julian,
looking deaper into the database path, I found a JSL-script working fine referring to a 0.1MB database. The JSL-script causing "freezing" refers to a 0.8MB database.
