Problem Note 16094: Invalid characters might display when use SAS/ACCESS® Interface to ODBC to connect a SAS Unicode server to a Unicode database
In SAS® 9.1, incorrect data might display when you use SAS/ACCESS Interface to ODBC to connect a SAS Unicode server (which is a SAS UTF-8 session) to a Unicode database.
This can occur when you have national language data in Unicode on an English edition of Windows that is configured with an English locale.
The incorrect data appears because the ODBC engine is not designed to enable Unicode processing.
To display Unicode data correctly, you need to change the Windows system locale so that it matches the language in which you are going to read. The SAS session locale must also be the same.
For example, if your database stores Japanese data with UCS2 encoding, you need to change the Windows locale to Japanese.
To to this, select Start ► Control Panel ► Regional and Language Options ► Advanced ► Japanese. You also need to set your SAS session locale to Japanese.
Select the Hot Fix tab in this note to access the hot fix for this issue.
This hot fix enables you to use a SAS UTF-8 session to access Unicode in
databases that are in an English-language working environment.
Beginning with SAS 9.2 Phase 2, SAS supports Unicode processing.
Earlier editions of SAS 9.2 still need to apply the hot fix.
Operating System and Release Information
SAS System | Base SAS | 64-bit Enabled Solaris | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
64-bit Enabled HP-UX | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
64-bit Enabled AIX | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Windows Vista | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows NT Workstation | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Professional | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows 2000 Server | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft® Windows® for x64 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
HP-UX IPF | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Linux | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Linux on Itanium | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
OpenVMS Alpha | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Tru64 UNIX | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
In SAS® 9.1, the ODBC engine was not designed for Unicode processing. This note explains how to change your system to display Unicode data. SAS 9.2 does not have issues with Unicode processing.
Type: | Problem Note |
Priority: | high |
Topic: | SAS Reference ==> Procedures ==> ACCESS
|
Date Modified: | 2009-10-27 14:47:35 |
Date Created: | 2005-09-02 16:21:09 |