Tag: SAS dummy

Chris Hemedinger 1
Confessions of a SAS Dummy

SAS Global Forum 2014 was a ton of fun, and extremely busy for yours truly. If you wonder how I spent my time at the conference, you need only to visit the on-demand video archive and see how many of the various sessions feature my shiny head. In most of

Chris Hemedinger 4
Be a code poet laureate

The next time you write a DATA step, try to express it in iambic pentameter.  Or instead of a SAS macro function, how about a SAS macro sonnet?  (Or, for the more base among you, a limerick?) That's the spirit behind the code {poems} project.  You write a poem in

Chris Hemedinger 3
Poetry on our own terms

Within the SAS documentation there must be thousands of unique words.  But ten words occur more than any others within the SAS documentation corpus: SAS, data, statement, option, set, value, variable,  PROC, model, table. This is according to one of our staff terminologists, Vicki Leary, who helps to keep our use of these words consistent and

Chris Hemedinger 4
Putting the "Guide" in Enterprise Guide

Some of you will remember that in the very early versions of SAS Enterprise Guide, we introduced a unique approach to helping you to learn SAS: an animated "agent" who could suggest your next steps within your project. We furloughed the agent (who appeared usually as a wizard, genie, or

Chris Hemedinger 2
SAS programming for the faint of heart

When we published the first edition of SAS For Dummies a couple of years ago, we received feedback from readers around the topic of SAS programming. In the book's introduction, we stated that the book doesn't cover the SAS programming language, but that there are many other fine books that

Programming Tips
Chris Hemedinger 8
In the year 9999...

...if man is still alive, will he be importing Excel spreadsheets and wondering why his leap years are off? I received this report from SAS Technical Support, on behalf of a customer who uses SAS Enterprise Guide to import spreadsheet data: The date "12/31/9999" will import as "02Jan****" when reading

1 2 3 4