Problem Note 62530: The EXPORT procedure adds extra spaces for Microsoft Access character variables within tables when you use certain WLATIN or LATIN encodings
 |  |  |  |  |
When you use PROC EXPORT to create Microsoft Access tables, character variables within the tables might be padded with extra spaces.
This issue can occur when all of the following are true:
- You use PROC EXPORT with the DBMS=ACCESSCS option.
- You use WLATIN (Microsoft Windows) or LATIN (UNIX) encoding that is not WLATIN1 or LATIN1. For example, you use WLATIN9 or LATIN9.
- You install one of these hot fixes:
You might also observe the extra spaces when you use other procedures (such as PROC SQL) or SAS DATA steps that update Microsoft Access tables.
The only noticeable effect is the increased size of the affected Microsoft Access table. Within Access, if you select the data in a cell, you can see that both the white space and data value are highlighted.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | Base SAS | Microsoft® Windows® for x64 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 |
| Microsoft Windows 8 Enterprise 32-bit | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows 8 Enterprise x64 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows 8 Pro 32-bit | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows 8 Pro x64 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows 8.1 Enterprise x64 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows 8.1 Pro 32-bit | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows 8.1 Pro x64 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows 10 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows Server 2008 | 9.4_M4 | 9.4 TS1M4 | ||||
| Microsoft Windows Server 2008 R2 | 9.4_M4 | 9.4 TS1M4 | ||||
| Microsoft Windows Server 2008 for x64 | 9.4_M4 | 9.4 TS1M4 | ||||
| Microsoft Windows Server 2012 Datacenter | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows Server 2012 R2 Std | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Microsoft Windows Server 2012 Std | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Windows 7 Enterprise 32 bit | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Windows 7 Enterprise x64 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Windows 7 Home Premium 32 bit | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Windows 7 Home Premium x64 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Windows 7 Professional 32 bit | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Windows 7 Professional x64 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Windows 7 Ultimate 32 bit | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Windows 7 Ultimate x64 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| 64-bit Enabled AIX | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| 64-bit Enabled Solaris | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| HP-UX IPF | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Linux for x64 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
| Solaris for x64 | 9.4_M4 | 9.4_M6 | 9.4 TS1M4 | 9.4 TS1M6 | ||
A fix for this issue for SAS/ACCESS Interface to PC Files 9.4_M5 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/B7U.html#62530A fix for this issue for SAS/ACCESS Interface to PC Files 9.4_M4 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/A7I.html#62530| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2018-07-27 15:35:23 |
| Date Created: | 2018-06-27 09:22:49 |