Date: Thu, 16 Apr 1998 22:20:12 -0700
Reply-To: "W. W. Viergever" <wwvierg@POP03.CA.US.IBM.NET>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: "W. W. Viergever" <wwvierg@POP03.CA.US.IBM.NET>
Subject: Re: Re[2]: Stats background of a Sas programmer
In-Reply-To: <9804168927.AA892786439@jane.hccompare.com>
Content-Type: text/plain; charset="us-ascii"
At 12:35 PM 4/16/98 -0600, Jack Hamilton wrote:
>"William W. Viergever" <wwvierg@IBM.NET> wrote:
>
>>Been a SAS code dog since the mid 70's (econometric class in econ grad
school,
>>graduate work doing anti-trust stuff in meat packing, banking, and oil,
then on
>>to post-pre-lim's employment doing HCFA, NIH and NCJSR research, starting on
>>360 boxes running MVS/MVT under Wylbur,
>
>Is anyone besides Stanford still using WYLBUR? I suppose Interact is
>still around somewhere.
>
Yup, NIH.
>>Just out of curiosity, what might you prefer to SAS for your reporting
and data
>>manipulation needs?
>
>Its object model is not satisfactory (that will get better in V7) and
>its GUI creation tools are poor compared to those in Visual Basic and
>various other Windows-based programs (also supposed to improve in V7).
>
Jack:
These points are well taken; however, they are GUI issues.
I'd (almost<G>) bet my house that I can out-manipulate data with SAS
vis-a-vis VB and other Windows apps (e.g., take "detailed" UB-92 data, pass
through it, reading procedure codes and POS and TOS values to map/capture
the quantity/Unit of Service (UOS) values into ICU/MS/CCU/OB/Nur/etc days
and dollar buckets, capture *only* dollars from ancillary proc codes, etc.,
etc., then output a single record that encapsulates all relevant/desired
info from the stay).
Now, being an old code dog, I may be tied to my tools too tightly {TTMTT?)
(i.e., VB may manipulate *as well* as SAS>, but then, can VB do stats <g>?
Later
| 
