Date: Thu, 7 Aug 2008 17:10:40 -0500
Reply-To: "./ ADD NAME=Data _null_," <iebupdte@GMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "./ ADD NAME=Data _null_," <iebupdte@GMAIL.COM>
Subject: Re: removing hidden characters
Content-Type: text/plain; charset=ISO-8859-1
To follow up. Using 's' as I suggested is not correct. Or at least
not for what I think we/I want to do. I was doing similar by with a
variable in a SAS data set.
Any way the correct COMPRESS that I ended up using is
x = compress(x,,'wk');
Keep writable characters.
On 8/7/08, ./ ADD NAME=Data _null_, <firstname.lastname@example.org> wrote:
> On 8/7/08, Chang Chung <email@example.com> wrote:
> > On Thu, 7 Aug 2008 14:48:00 -0500, ./ ADD NAME=Data _null_,
> > <iebupdte@GMAIL.COM> wrote:
> > >You may be able to just remove the characters without knowing what the are...
> > hi,
> > i would not recommend a cure without knowing the cause. ... Well, dr. house
> > (on tv) seems to be doing this all the time, so maybe it is ok for such an
> > expert like data _null_ to do this...
> Yes I agree knowing the cause is good. Plus I try to be nicer to
> people than Dr. H.
> I was not actually suggesting not knowing the "cause" just not knowing
> the values that need to be "cleaned".
> > before reading it into sas, i would either checksum the file, or even ftp
> > back to the source and compare the files just to make sure that the data are
> > not corrupted during the file transfer.
> The LIST statement is also good to examine input records, using SAS.
> Plus the automatic HEX display is nice when there are non printable
> > just my two cents...
> > cheers,
> > chang