Bug in import sas

[KitBaum]

Stata Tech Support has verified that there is a bug in version 16.1 import sas. If a SAS dataset (sas7bdat) has observations containing NaN (not a number) fields, they are not mapped into Stata missing values, but retained as such. The data import without any errors, but use of a command like codebook will cause Stata to enter an infinite loop, from which a force quit is the only solution. It is likely that any command that sorts the data on a variable containing NaNs will cause the same problem.

[William Lisowski]

A similar bug exists for import delimited when you have your default type set as double, as described at post #13 of the very long discussion at

https://www.statalist.org/forums/for...0-not-a-number

[Hua Peng (StataCorp)]

Thanks for bringing this to our attention. We are in the process of fixing it in a future Stata 16 update. We are also reviewing other import commands (import spss, import excel, and odbc) to see if similar issues exist.