Database table scripts (Update from Database, Modify, etc.) or .jmpquery files stop working. These table scripts may also produce an error indicating the column, or table could not be found.
When the preference Tables > Hide ODBC Connection String is selected, JMP removes the connection string from the imported table's table scripts: Source, Update From Database, Update from DB, and Modify Query. It also removes the connection string from any .jmpquery files that have been saved.
If the above is not the desired behavior, deselect this preference to maintain the connection string within the table scripts (Source, Update From Database, Update from DB, and Modify Query) or the .jmpquery file.
JMP removes the table scripts Source, Update From Database, Update from DB, and Modify Query. It also removes the connection string from any .jmpquery files that have been saved. In JMP 17.1 and newer, opening any .jmpquery files that have been saved will produce a database login prompt to enter your User ID and password, or Change Data Source. Select Change Data Source and select your DSN to connect to your data source.
If the above is not the desired behavior, deselect this preference so the table scripts are maintained within the before-mentioned table scripts and the connection string is maintained within the .jmpquery file.
Updating this preference is not retroactive. You will have to import the data set again to maintain the table scripts and connection strings or recreate the .jmpquery file so the connection string is maintained in the table scripts or .jmpquery file.