Date: Thu, 1 Oct 2009 17:46:53 -0400
Reply-To: Arthur Tabachneck <art297@NETSCAPE.NET>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Arthur Tabachneck <art297@NETSCAPE.NET>
Subject: Re: PROC IMPORT Bug in 9.2 TS2M0
If you are indicating that the new proc import will treat any or even some
4-digit numbers as being datetime variables, I would hope that SAS kept
staff overtime to correct the situation.
Can any birdies confirm?
On Thu, 1 Oct 2009 17:26:51 +0000, Deborah Testa
>My years-old PROC IMPORT code broke in 9.2 TS2M0. Here's an explanation
>and a suggested work-around from SAS tech support:
>The algorithm to determine if a value is a date, datetime or time was
>changed in SAS 9.2. Unfortunately it looks like there is a problem with
>typing some of the values to determine if the value is a date, time or
>datetime. I will report this problem to the developer. In the
>meantime, you will need to recall the generated DATA step code assuming
>you are using PROC IMPORT in interactive mode. To recall the generated
>DATA step code, you will need to make certain you have the EDITOR window
>active and then do a RUN-RECALL LAST SUBMIT after the PROC IMPORT has
>run. The generated DATA step will appear in the Editor Window and you
>can change the INFORMAT, FORMAT and INPUT statement for the 2 variables,
>VSBT and GNDRCODE, so they are read in as character. Then you will
>resubmit the generated DATA step code to receive expected results.
>Since I still have SAS 8.2 installed, I'm going to run my PROC IMPORT
>steps in 8.2 rather than introduce the manual step into the middle of an
>automated series of steps.
>My data contains codes for gender (2201 for Male and 2202 for Female).
>When I read those values from a .csv file into SAS using PROC IMPORT,
>SAS creates a numeric variable (fine) but uses a datetime. format and
>the anydtdtm40. informat. , creating raw values of 1956614400 and