Problem Note 9914: /UNIQUE option does not work with ODBC engine for character typed
variables
Specifying the /UNIQUE option on a SET statement causes the KEY=
search to always begin at the "top" of the index. Starting in
Version 8 TSLEVEL M0, if there are consecutive duplicate KEY= values
in the transaction data set and unique index values in the master data
set, SAS incorrectly matches only the first occurrence of the index
value from the transaction data set.
The lookup process works correctly for numeric variables starting in
Release 8.1 TS1M0.
A Technical Support hot fix for Release 8.2 (TS2M0) for this
issue is available at:
http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#009914
Operating System and Release Information
| SAS System | SAS/ACCESS Interface to ODBC | Microsoft Windows NT Workstation | 8 TS M0 | 9.1 TS1M0 |
| 64-bit Enabled AIX | 8 TS M0 | |
| 64-bit Enabled HP-UX | 8 TS M0 | |
| HP-UX | 8 TS M0 | |
| ABI+ for Intel Architecture | 8 TS M0 | |
| Microsoft Windows 95/98 | 8 TS M0 | |
| Microsoft Windows 2000 Server | 8 TS M0 | 9.1 TS1M0 |
| Microsoft Windows 2000 Professional | 8 TS M0 | 9.1 TS1M0 |
| Microsoft Windows 2000 Datacenter Server | 8 TS M0 | 9.1 TS1M0 |
| Microsoft Windows 2000 Advanced Server | 8 TS M0 | 9.1 TS1M0 |
| OS/2 | 8 TS M0 | |
| Solaris | 8 TS M0 | 9.1 TS1M0 |
| 64-bit Enabled Solaris | 8 TS M0 | 9.1 TS1M0 |
| IRIX | 8 TS M0 | |
| AIX | 8 TS M0 | |
| Tru64 UNIX | 8 TS M0 | 9.1 TS1M0 |
*
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.
| Type: | Problem Note |
| Priority: | high |
| Topic: | Third Party ==> Information Exchange ==> ODBC (Open Database Connectivity)
SAS Reference ==> LIBNAME Engines
|
| Date Modified: | 2003-06-20 10:28:33 |
| Date Created: | 2003-04-29 15:44:30 |
