LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (July 2005, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Wed, 27 Jul 2005 09:33:55 -0500
Reply-To:     "A. Michielsen" <amichielsen@COMCAST.NET>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "A. Michielsen" <amichielsen@COMCAST.NET>
Organization: Your Company
Subject:      Re: transport file from v9.1
Comments: To:

As you have discovered - both the xport engine and proc cport require valid sas version 6 elements - and you have at least one element (a variable name) that is invalid - as you have indicated. You _may_ be able to use proc sq to read the data with the invalid name. If it doesn't work as Proc Sql; Select * from...; Then try: Proc Sql; Select 'RESPONDENT_ID'n, ... That's how EG allows (supports) invalid column names with SQL that aren't allowed in a Data Step.

saslist@COMCAST.NET (saslist) wrote in

> I seem to be having some difficulty creating a transport file from > version 9. I usually just use the xport engine but I get: > > libname outdd xport 'c:\sectIIb.v5x'; > data outdd.sectIIb; > set work.sectIIb; > > ERROR: The variable name RESPONDENT_ID is illegal for the version 6 > file OUTDD.SECTIIB.DATA > > Needless to say I have not heeded the 8 character variable name limit. > Sooo, I use proc cimport: > > filename tranfile 'c:\section2.v5x'; > proc cimport lib=work file=tranfile; > run; > > However, the person who will be using this is using version 8 and gets > an error that they cannot import the version of the file I am > creating. Have I missed an option?

Back to: Top of message | Previous page | Main SAS-L page