| P4Q004 |
| SAS/ACCESS Interface to PC Files 9.4_M8 |
| Issue(s) Addressed: | Introduced: |
| KB0041165 | The EXPORT procedure should trigger an error message when you define a location for the OUTFILE through a FILENAME statement and the path is invalid |
P4Q001 |
| 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 |
P4Q001 |
| 70404 | PROC SCAPROC inserts an additional forward slash (/) in path names in JOBSPLIT information when executed on UNIX systems |
P4Q001 |
| 70709 | A memory corruption vulnerability exists in Base SAS® and SAS/STAT® |
P4Q001 |
| 71106 | Using SAS/ACCESS® Interface to PC Files with the XLSX engine and spaces within the file name result in a Segmentation Violation |
P4Q001 |
| KB0041575 | The error "ERROR: File MYLIB7X.'Sheet1\$'.DATA does not exist" occurs in SAS/ACCESS® Interface to PC Files |
P4Q002 |
| KB0043167 | Exporting SAS data to STATA file adds an extra byte to the character column length of the target STATA file |
P4Q003 |
| KB0042166 | Using the OBS= data set option with Azure Synapse also limits the number of columns |
P4Q004 |
NOTE: If you install this hot fix and have SAS/ACCESS Interface to DB2 9.45 installed, you must also install hot fix M5Z004.
If you install this hot fix and have SAS/ACCESS Interface to Microsoft SQL Server 9.46 installed, you must also install hot fix M5F007.
If you install this hot fix and have SAS/ACCESS Interface to ODBC 9.4_M8 installed, you must also install hot fix M3G005.
If you install this hot fix and have DataDirect ODBC Driver for Amazon Redshift 9.45 installed, you must also install hot fix M2D008.
If you install this hot fix and have DataDirect ODBC Driver for Greenplum 9.45 installed, you must also install hot fix M9F005.
If you install this hot fix and have DataDirect ODBC Driver for Microsoft SQL Server 9.45 installed, you must also install hot fix M2L010.
|
|
|
General Information about Hot Fixes