| J9M014 for 64-bit Enabled Solaris |
| SAS/ACCESS Interface to PC Files 9.4_M7 |
| Issue(s) Addressed: | Introduced: |
| 67398 | The message "ERROR: Invalid physical name for library…" is displayed when you access a library with the XLSX engine |
J9M001 |
| 67719 | The EXPORT procedure with the DBMS=XLSX argument creates a Microsoft Excel file with incorrect date attributes in its internal metadata |
J9M002 |
| 67934 | PROC IMPORT with the DBMS=XLS option creates wrong output data when an Excel file has hidden sheets |
J9M003 |
| 67320 | A corrupted Microsoft Excel file might be created with DBMS=XLSX when the worksheet name contains 8-bit characters |
J9M004 |
| 68093 | Errors occur when you use the XLSX LIBNAME engine to read a file with the .xlsm file extension |
J9M005 |
| 68383 | An error in PROC EXPORT might not appear in the SAS® Enterprise Guide® Log window |
J9M006 |
| 68476 | The message "We found a problem with some content in filename.xlsx" might appear when you open a SAS generated XLSX file in Microsoft Excel |
J9M007 |
| 68535 | An XLSX file that is created by using PROC EXPORT does not open in Microsoft Power BI |
J9M007 |
| 68654 | Using a FILENAME fileref in PROC EXPORT with DBMS=XLSX overwrites the existing sheet |
J9M008 |
| 69799 | Using the XLS engine with PROC IMPORT transcodes 8-bit characters to UTF-8 regardless of the SAS® Session encoding in SAS® 9.4M7 |
J9M010 |
| 70238 | Using the IMPORT procedure with a comma-delimited .dbf file in SAS® 9.4M7 (TS1M7) and SAS® 9.4M8 (TS1M8) can result in a Segmentation Violation |
J9M011 |
| 70349 | An import of an XLS file fails with "Requested Sheet Name not found on Excel" when the worksheet contains NLS characters |
J9M012 |
| 70404 | PROC SCAPROC inserts an additional forward slash (/) in path names in JOBSPLIT information when executed on UNIX systems |
J9M013 |
|
General Information about Hot Fixes