B7U005 for Windows |
SAS/ACCESS Interface to PC Files 9.4_M5 |
Issue(s) Addressed: | Introduced: |
61434 | CHARACTER variables are doubled in length when you import an Excel file using the SAS® PC Files Server on a non-wlatin1 SAS® session |
B7U001 |
61853 | "WARNING: The length of column 1 exceeds the maximum of 254 allowed by dBASE..." might occur when you use the EXPORT procedure |
B7U002 |
62530 | The EXPORT procedure adds extra spaces for Microsoft Access character variables within tables when you use certain WLATIN or LATIN encodings |
B7U003 |
63170 | "Unable to transcode data to/from UCS-2 encoding" occurs after invalid characters are read in an Amazon Redshift, Impala, Netezza, or PostgreSQL table |
B7U003 |
63327 | The XLSX engine does not read certain characters in data exported using the SAS® Enterprise Guide® export wizard |
B7U003 |
63328 | "Unable to transcode data to/from UCS-2 encoding" occurs when you import with SAS® PC Files Server (DBMS=EXCELCS) using Latin9 |
B7U003 |
63830 | The EXPORT procedure with the DBMS=SPSS option in SAS® 9.4M5 creates SAV files that are larger in size than expected |
B7U004 |
67320 | A corrupted Microsoft Excel file might be created with DBMS=XLSX when the worksheet name contains 8-bit characters |
B7U005 |
NOTE: If you install this hot fix, you must also install hot fix B6Q099 for Base SAS 9.4_M5. |
|