SAS Communications #5 Nov 1975
The fifth issue of “SAS Communications” came out in 1975 (we don’t have a copy of issue #4). Highlights include some updates to SAS-75, the formation of the first SAS User Groups (Chicago and Florida), and personnel updates regarding Jolayne Servi...
SAS Communications #3 Dec 1974
The third issue of “SAS Communications” was published in December 1974 by the SAS Project Group. Highlights of this issue include an interview with Tony Barr, the announcement of SAS-75 (to b...
SAS Communications #2 May 1974
In May 1974 the second issue of “SAS Communications” was published by the SAS Project Group. Within these pages you discover fascinating insights into the early days of SAS. A PDF of the original is available
SAS Communications 1973-1979
In December 1973 the first issue of “SAS Communications” was released to the SAS User Community. Below is an extract of issue #1 - a unique and fascinating account of the early days (and members) of the SAS Project Group. A PDF of the original is...
Loading files to SAS with CURL
A useful feature of SAS Stored Processes is the ability to load multiple files in a single request. This could be a bunch of CSVs for processing, or even a I’ve said it before and I’ll say it again - SAS is an unparalleled platform for light....sas program that you want to Using CURL with SAS Stored Processes
The Performance of Dosubl vs Call Execute
Both dosubl and call execute accept raw SAS code as input. The difference between them is that call execute will take your code and add it to the stack (so, after your data step completes) whilst dosub...
Think you know SAS? Take the Sasensei Challenge
Think you know SAS? Take the Sasensei challenge! We’ve developed a question based learning system that will put your SAS knowledge to the test. Sasensei is a kick ass ninja training tool for an expanding range...
Tabs v Spaces - which is more popular in SAS?
Tabs or Spaces? Does it even matter, so long as you / your team are consistent? For many SAS developers the standard place to write code is the Program Editor - for which the default setting is to use tabs, else 4 spaces.
Interestingly - ...
Look out - Locale Gotcha
As gotcha’s go, this was a good one!
We had a report being generated with dates that were inconsistent with the source file (MMDDYY instead of DDMMYY), but only for certain records. This was definitely related to the « Older Entries
