Support

Latest Notes

• Query Builder or Open Table Error: The specified DSN contains an architecture mismatch between the Driver and Application.

  Whether you prefer to use Open Table or Query Builder in JMP®, you may encounter the error: "The specified DSN contains an architecture mismatch between the Driver and Application" (Figure 1.1). Figure 1.1 Figure 1 With Database Management Systems (DBMS) such as Oracle, MS SQL Server, PostgreSQL, etc., you need to configure the ODBC Data Source that corresponds with the architecture of JMP. Meanin...

  Dahlia_Watkins

  JMP Knowledge Base |

  Dec 23, 2022 7:49 AM

  689 views | 0 replies

• Post-Query Script within Query Builder is ignored when launching a saved .jmpquery file.

  In JMP® 15 when a post-query script is saved within a .jmpquery file, the script is ignored upon opening the file and selecting Run Query. The table being referenced within the query returns data, but the expected output of the post-query script is not generated. Workaround: Open the Query Builder (.jmpquery) file.Select the Red-Triangle > Run on Open.If the script is still listed, copy the Post-Q...

  Dahlia_Watkins

  JMP Knowledge Base |

  Dec 23, 2022 7:45 AM

  389 views | 0 replies

• JMP® Query Builder: Filters set with Prompt on Run crash JMP 15.

  Selecting "Prompt on Run" for a variable within Query Builder's filter crashes JMP® 15 after selecting "Run Query". Workaround: Go to File > Preferences > Query Builder and turn off "Run queries in the background when possible".   [Previously JMP Note 65168]

  Dahlia_Watkins

  JMP Knowledge Base |

  Dec 23, 2022 7:41 AM

  174 views | 0 replies

• JMP® Get Data for x fails using R 4.2.x and later

  R 4.2.x versions are currently not working with various JSL R functions that pull data from R. To address this issue, SAS recommends that you downgrade to an R 4.1.x version to use the R integration with JMP. Note: Reference JMP Note 575310 when considering using the integration on Apple (macOS) silicon arm (M1) architecture.   [Previously JMP Note 69504]

  Dahlia_Watkins

  JMP Knowledge Base |

  Dec 23, 2022 2:29 AM

  672 views | 0 replies

• JMP® does not support Anaconda Python distributions on Macintosh

  Macintosh no longer allows modifications to paths to Anaconda libraries that JMP depends on at runtime. As such, JMP no longer supports the Anaconda distribution of Python. JMP recommends the use of the Python.org distribution on Macintosh when using the Python integration.    [Previously JMP Note 67963]

  Dahlia_Watkins

  JMP Knowledge Base |

  Dec 23, 2022 2:24 AM

  281 views | 0 replies

• JMP® 15 Google Sheets: sign in disabled for app or app is not secure

  Using the JMP® 15 Google Sheets import results in one of the following messages:  Sign in with Google temporarily disabled for this app.Couldn't sign you in. This browser or app may not be secure.  Due to recent security changes, importing Google Sheets via File > Internet Open > Google Sheets might present these messages. The messages are the result of changes in how Google grants applications ac...

  Dahlia_Watkins

  JMP Knowledge Base |

  Dec 23, 2022 2:22 AM

  390 views | 0 replies

• JMP® 15 does not recognize tables when opening .mdb or .accdb files.

  Tables produced by opening a .accdb or .mdb file are not recognized when using the drag and drop method or using File > Open. As a result, any subsequent actions, such as choosing Analyze > Fit Y by X or selecting the table from the Current Data Table drop-down will not see the opened table. Workaround: Run the source script within the table, which produces a new table that is recognized. Import t...

  Dahlia_Watkins

  JMP Knowledge Base |

  Dec 23, 2022 2:19 AM

  343 views | 0 replies

• JMP® 15 and newer will not install on 32-bit operating systems

  If you install JMP 15 or a newer version, you might encounter an error message that is similar to the following: The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) versions of the program, and then contact the software publisher. This message appears when you are lik...

  Dahlia_Watkins

  JMP Knowledge Base |

  Dec 23, 2022 2:15 AM

  557 views | 0 replies

• How to re-register the Excel Add-in for JMP® if it is missing

  If the Excel Add-in for JMP® was once visible in Excel but is no longer listed in the menu, follow these steps to correct the problem. This may occur when the file used to load the add-in becomes unregistered. To register or re-enable the Excel Add-in for JMP: Close Excel.Launch the Command Prompt in Windows. See 10 ways to launch the Command Prompt in Windows for your specific Windows version.Rig...

  Dahlia_Watkins

  JMP Knowledge Base |

  Dec 23, 2022 1:58 AM

  3061 views | 0 replies

• Determining your ODBC driver version when you contact JMP® for database-related questions

  This JMP Note describes the steps you can take to determine your Open Database Connectivity (ODBC) driver version. Take these steps if you are using a Microsoft Windows PC: Open JMP.Navigate to Help ► About JMP.If you are running JMP^® 15 and higher, your system architecture is 64-bit. Otherwise, it lists as 32-bit in this area.Navigate to Control Panel ► System and Security ► Administrative Tools....

  Dahlia_Watkins

  JMP Knowledge Base |

  Dec 23, 2022 1:50 AM

  1184 views | 0 replies

• #REF values appear in JMP® data tables when importing from Excel®

  When importing .xlsx, or .xls workbooks into JMP®, #REF values may appear within a variable. This is a known issue that stems from Excel formulas that are nested or conditional. The utility used to import the workbook does not process these formulas, which leads to missing cell references (#REF).  Workarounds:  Save the .xlsx or .xls workbook as a text (.txt) file and import the data into JMP.Use ...

  Dahlia_Watkins

  JMP Knowledge Base |

  Dec 23, 2022 1:40 AM

  351 views | 0 replies

• JMP® Clinical might crash when you attempt to close the Review Builder via an API call

  When you attempt to close the Review Builder via an API call, JMP Clinical might crash. This issue is corrected in the JMP^® Clinical 7.1.2 hot fix (link below).   JMP^® Clinical 7.1.2 hot fix   [Previously JMP Note 65971]

  sseligman

  JMP Knowledge Base |

  Dec 22, 2022 12:13 PM

  553 views | 0 replies

• JMP® Clinical 7.1 displays a zero size on disk for studies containing .xpt files that are changed to .sas7bdat files

  For a study that contains transport (.xpt) files, JMP^® Clinical reports a nonzero size on disk. However, if the .xpt files are replaced with the corresponding .sas7bdat files (and the study metadata is refreshed), a size on disk of zero is reported. This issue is corrected in the JMP^® Clinical 7.1.2 hot fix (link below).   JMP^® Clinical 7.1.2 hot fix   [Previously JMP Note 65972]

  sseligman

  JMP Knowledge Base |

  Dec 22, 2022 12:11 PM

  381 views | 0 replies

• JMP® Clinical 7.0 produces errors "This file could not be saved with the given name" and "Unable to save file" when trying to save a review

  In JMP® Clinical 7.0, if a review that has been previously saved is open in Review Builder, and the user also opens it in Review Viewer, making changes to the review in Review Builder and trying to save it results in the following errors: "This file could not be saved with the given name." "Unable to save file." This error is resolved in the JMP® Clinical 7.0.1 hotfix (link below).   JMP® Clinical...

  sseligman

  JMP Knowledge Base |

  Dec 22, 2022 12:09 PM

  290 views | 0 replies

• JMP® Clinical 7.0 produces an error when ARM variable is missing and multiple TRT0xA or TRT0xP variables exist

  When an ARM variable does not exist but TRT0xA or TRT0xP variables do exist, distribution reports produce the following error: could not find column in access or evaluation of 'Column' , Column/*###*/("Trt") Selecting TRT01A or TRT01P as the treatment variable to use also produces the error. If you add ARM to the data set or select ARM as the comparator to use, no error occurs. This error is commo...

  sseligman

  JMP Knowledge Base |

  Dec 22, 2022 11:42 AM

  351 views | 0 replies

• JMP® Clinical 7.0 can crash when adding a study or refreshing study metadata

  When attempting to add a study or refresh study metadata, JMP® Clinical can crash. The crash might be due to specification of a Universal Naming Convention (UNC) path, which uses double slashes or backslashes to precede the name of the computer.  Go to the Settings tab, then click on the Manage Configurations button to examine the path settings. If <userLocal> or /user/clinical/output contains a U...

  sseligman

  JMP Knowledge Base |

  Dec 22, 2022 11:39 AM

  316 views | 0 replies

• Error when converting dates to character dates in JMP® Clinical 7.1

  In JMP^® Clinical 7.1 when the AE dataset is loaded and ASTDT and/or AENDT are converted to AESTDTC and/or AEENDTC, the length is not long enough, and all values of the character dates are incorrect. This issue is resolved in the hot fix found here. If you encounter this problem and if the study was previously added with JMP^® Clinical 7.1 before installing the hot fix in this note, you will need to...

  laura_archer

  JMP Knowledge Base |

  Dec 22, 2022 9:40 AM

  334 views | 0 replies

• Error in the Patient Profile in JMP® Clinical 6.1

  This Hotfix allows the Patient Profile to better support character findings in the profile graphic display and in the domain tables.  Additionally, new options in the Patient Profile allow horizontal or vertical orientation of findings taken across timepoints.  To use these changes, apply the Hot fix found here.   [Previously JMP Note 60236]

  laura_archer

  JMP Knowledge Base |

  Dec 22, 2022 9:37 AM

  271 views | 0 replies

• Enhancements to JMP® Clinical 7.1

  The following is a list of enhancements to JMP Clinical 7.1, found in the JMP Clinical 7.1.1 hot fix. Adverse Event Narrative: Use CMCAT/MHCAT to determine the subset of CM/MH records to use: 
  
  For the ByNarrativeCategoryDetails template, the following has been added:
  
  For prior and concomitant medications, JMP Clinical looks to see if CMCAT = "PRIOR AND CONCOMITANT MEDICATIONS" exists as a category i...

  laura_archer

  JMP Knowledge Base |

  Dec 22, 2022 7:54 AM

  425 views | 0 replies

• DMSUPP population flags are no longer picked up in metadata for Dialog Population options

  DMSUPP population flags no longer picked up in metadata for Dialog Population options.  This hot fix resolves this issue.  Due to a differentiation of &ADSLVARS to have &ADSLSUPPVars this hot fix updates the Add/Manage Study mechanism to include flags found in DMSUPP.   After the hot fix is applied the study metadata needs to be refreshed. The  hot fix is found here.     [Previously JMP Note 61810...

  laura_archer

  JMP Knowledge Base |

  Dec 22, 2022 7:52 AM

  289 views | 0 replies

• DM Distribution cannot be run when SUPPDM missing IDVAR and IDVARVAL

  DM Distribution returns an error when a SUPPDM domain is present but does not contain IDVAR and IVARVAL.  No error is returned if the variables exist but are empty.  The hotfix found here resolves this error.   [Previously JMP Note 61809]

  laura_archer

  JMP Knowledge Base |

  Dec 22, 2022 7:50 AM

  302 views | 0 replies

• Changing report options in JMP® Clinical 6.1 are not honored until the report is rerun

  JMP® Clinical 6.1 reviews might show incorrect report options. When an option on a report in JMP Clinical 6.1 is changed and the report is not rerun, the review is saved with incorrect report options which do not match the results. To resolve the problem, apply the Hotfix found here.   [Previously JMP Note 60235]

  laura_archer

  JMP Knowledge Base |

  Dec 22, 2022 7:48 AM

  267 views | 0 replies

• ByNarrativeCategoryDetails template incorrectly states con meds=none

  In JMP^® Clinical 7.1 an AE narrative using the template ByNarrativeCategoryDetails might result in incorrect output where Concomitant Medications are "None" for ALL AEs. This issue is resolved in the JMP^® Clinical 7.1.1 hot fix. To resolve the problem, apply the hot fix found here.   [Previously JMP Note 65318]

  laura_archer

  JMP Knowledge Base |

  Dec 22, 2022 7:46 AM

  379 views | 0 replies

• An Adverse Events Distribution in JMP® Clinical 8.0 might result in an error when calculating relative risk

  In JMP Clinical 8.0, an Adverse Events Distribution might result in the following error when calculating relative risk: ERROR: More positional parameters found than defined. This error can occur when values in the data contain commas. Click here to access the hot fix for this issue.   [Previously JMP Note 67905]

  laura_archer

  JMP Knowledge Base |

  Dec 22, 2022 7:44 AM

  385 views | 0 replies

• An Adverse Event Narrative in JMP® Clinical 8.0 might be missing information about dates from ADaM data sets

  An Adverse Event Narrative that is created in JMP Clinical 8.0 might not display some dates correctly when you are using Analysis Data Model (ADaM) data sets with ASTDTM and AENDTM. Although there are dates in the data sets, the Adverse Event Narrative does not have the appropriate sentences that reflect the treatment dates. These statements are missing from the output.   Click here to access the ...

  laura_archer

  JMP Knowledge Base |

  Dec 22, 2022 7:42 AM

  404 views | 0 replies