Samples & SAS Notes > Common Programming Tasks
>
Reading and Writing SAS Data
| Date | Title | Type | ||
|---|---|---|---|---|
| 10/13/09 |
37283 - Use a Microsoft Excel file to create a user-defined format If you have an existing Excel spreadsheet containing variables and descriptions, you can easily transform it into a custom format. http://support.sas.com/kb/37/283.html, 20KB |
Sample | ||
| 10/13/09 |
24453 - Why do I sometimes get different results when I do a many-to-one merge in one datastep followed by a second datastep with subsetting conditions versus doing the merge and subset in one datastep? When you do a many-to-one merge, the variable values in the non-duplicate dataset will be retained and carry down the BY-Group. The values are not reinitialized to missing until the BY-Group changes. If you are doing a ... http://support.sas.com/kb/24/453.html, 31KB |
Usage Note | ||
| 10/5/09 |
37328 - SAS evaluates ALL the expressions in an IF statement All expressions in a IF statement are evaluated, even when the first one is false. http://support.sas.com/kb/37/328.html, 20KB |
Usage Note | ||
| 9/16/09 |
34232 - Incorrect results produced for numeric informats when reading extremely large numbers When reading a decimal number larger than will fit in a double-precision binary floating point variable, the resulting numeric field does not conform to IEEE standards for truncation in all cases. http://support.sas.com/kb/34/232.html, 27KB |
Problem Note | ||
| 4/3/09 |
35428 - Warning messages that incorrectly produce a RC=0 now correctly produce a RC=4 in SAS 9.2 Some warning messages incorrectly produced a RC=0 prior to SAS 9.2 http://support.sas.com/kb/35/428.html, 19KB |
Problem Note | ||
| 3/25/09 |
15989 - In the UNIX environment, SASŪ data set names and external file names must be lowercase In the UNIX environment, SAS writes data set names and external file names in all lowercase characters. Because of this, SAS reads only data set names that are written in all lowercase characters. In addition to SAS ... http://support.sas.com/kb/15/989.html, 18KB |
Usage Note | ||
| 3/17/09 |
34948 - Widths specified by informats on ATTRIB statement aren't passed properly When an informat is specified on the ATTRIB statement, the width of the data value should not exceed the width the informat can handle. When this occurs, an error is produced. ERROR: Read Access Violation In Task [ ... http://support.sas.com/kb/34/948.html, 20KB |
Problem Note | ||
| 1/20/09 |
34513 - Obtain the name of data set being read with SET statement with INDSNAME= option Prior to SAS 9.2, in order to obtain the name of the data set being read from a SET statement, the IN= data set option is required, along with hard coding the value. Beginning in SAS 9.2, the INDSNAME= option placed ... http://support.sas.com/kb/34/513.html, 20KB |
Sample | ||
| 10/2/08 |
33467 - WEEKU informat returns yearcutoff value when reading a missing value When the WEEKUw. informat reads a missing value, the value of the YEARCUTOFF= system option is returned as the value. The expected behavior is a result of a missing value and a note alerting the programmer of invalid ... http://support.sas.com/kb/33/467.html, 19KB |
Problem Note | ||
| 5/8/08 |
32009 - How to Use "Copy to SAS Server" to Write Back to your Original Data in Microsoft Excel The SAS Add-in for Microsoft Office currently does not have the capability to write back to the original table after modifying data in the spreadsheet. However, you can use the Copy to SAS Server to write the modified ... http://support.sas.com/kb/32/009.html, 22KB |
Sample | ||
