Problem Note 32702: Missing values can be incorrectly filled when you import a Microsoft Access file with the DBSASTYPE= option in a LIBNAME statement
Missing values can be filled incorrectly when you import a Microsoft Access file using the ACCESS engine in a LIBNAME statement that contains the DBSASTYPE= option.
For example, suppose you have the following data in your access database:
VAR1 VAR2 VAR3 VAR4
12 3.5 3 3
13 2.83 3.25 3.2
14
15 3.2 3
Then suppose you submit the following code, using the DBSASTYPE= option to read this data:
libname test_res "yourmdb.mdb";
data test_import;
set test_res.test_res (dbsastype=( var2 =numeric
var3 =numeric
var4 =numeric));
run;
In the resulting data, the missing values are now filled in with data from the previous row:
VAR1 VAR2 VAR3 VAR4
12 3.5 3 3
13 2.83 3.25 3.2
14 2.83 3.25 3.2
15 3.2 3 3.2
To circumvent this problem, do not use the DBSASTYPE= option to read the data.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to PC Files | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft® Windows® for x64 | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 | |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 | |
Microsoft Windows 2000 Server | 9.1 TS1M3 | |
Microsoft Windows 2000 Professional | 9.1 TS1M3 | |
Microsoft Windows NT Workstation | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows XP Professional | 9.1 TS1M3 | 9.2 TS1M0 |
Windows Vista | 9.1 TS1M3 | 9.2 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: | alert |
Date Modified: | 2008-09-10 09:13:01 |
Date Created: | 2008-07-18 11:22:53 |