Me thinks in SAS code <> is interpreted as NOT EQUAL,as shows this statement in the LOG:

1 proc print data=current.all_ae; 2 where day <> .; NOTE: The "<>" operator is interpreted as "not equals". 3 run;

where day ^= . also gives only observations with value equals MISSING! and when I try day NE . I get the message that NE is an unknown keyword.

where day > -99999999 gives me the NON-MISSING observations, but this is too much a bag of tricks for me!

So, me thinks SAS is not consistent!

Lex

"William W. Viergever" <wwvierg@IBM.NET> wrote in message news:4.3.1.2.20000419100657.00b1b960@pop3.attglobal.net... > Me thinks Lex probably codes VBA/VB as well as SAS <g>. > > <> in VBA/VB is "not equal" > > Late > > At 03:57 PM 04/19/2000, John Iwaniszek wrote: > >I will assume that you know that <> is max. I haven't a clue how your > >equation will evaluate in the where statement, but try using one of the > >NOT EQUALS TO operators like ^= or NE. > > > >John > > > >Lex Jansen wrote: > > > > > > Hi, > > > > > > In the SAS viewer (I tried version 6 and 8) I want to filter my data using a > > > where clause: > > > where day <> . (day is numeric) > > > When I do this it gives me the values that are missing. > > > > > > When I use this where clause: > > > where day = . > > > it gives the values that are non-missing. > > > > > > This sounds like a bug. > > > Does anyone know more about this ? > > > Thanks, > > -------------------------------------------------------------------------- -- > William W. Viergever Voice : (916) 483-8398 > Viergever & Associates Fax : (916) 483-8399 > A SAS Institute Quality Partner (USA) E-mail : wwvierg@ibm.net > Sacramento, CA 95825 > > "Duct tape is like the Force. It has a Dark Side. It has a Light Side. > It holds the Universe together." > > "Time flies like an arrow. Fruit flies like a banana." > - Groucho Marx > -------------------------------------------------------------------------- --