Date:         Tue, 29 Jul 2008 15:43:23 -0400
Reply-To:     "Howard Schreier <hs AT dc-sug DOT org>"
              <schreier.junk.mail@GMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Howard Schreier <hs AT dc-sug DOT org>"
              <schreier.junk.mail@GMAIL.COM>
Subject:      Re: ERROR: The value 3 is not a valid SAS name.

On Tue, 29 Jul 2008 12:05:35 -0700, Chris T <chris.tinnon@GMAIL.COM> wrote:

>Okay....
>
>So a transpose statement occurs and I have some field named the
>following:
>
>                         3
>                         4
>                         5
>                         40
>                         41
>
>I know these are not valid SAS variable names.  I am using enterprise
>guide and looked at the field names, copied them, pasted them into a
>hex viewer to see if the blank were any weird characters, no.  Just 4
>spaces, hex 20.  But why does the transpose procedure even execute
>with them?  How can it create a dataset with those names if it's not
>valid?  The job doesn't bomb on that step, but rather when the dataset
>it complete and another job sets it.
>
>Hopefully this is enough for some feedback.

Was the other job also run using EG?
See http://support.sas.com/kb/16/867.html

>
>I'm going back to crying.