The SAS Dummy
A SAS® blog for the rest of us![Reporting on SAS Information Maps](https://blogs.sas.com/content/sasdummy/files/2017/02/ProgrammingTips-3.png)
Like any good SAS professional, I subscribe to the SAS Samples RSS feed. The other day I found this sample that shows how to create a PDF report about the contents of a SAS Information Map. It's a nice example: it shows how to use the INFOMAPS engine and ODS
![Finding the FOREIGNers in your SAS environment](https://blogs.sas.com/content/sasdummy/files/2017/01/ProgrammingTips-2.png)
As Shane reveals on his blog, your SAS session is equipped to read data that are encoded for all types of machine architectures and locales. ASCII, EBCDIC, 32- or 64-bit, English, Japanese, Greek, Hebrew: the list goes on and on. SAS accomplishes this by using a feature called Cross-Environment Data
![Getting out of SORTs with SAS data](https://blogs.sas.com/content/sasdummy/files/2017/01/ProgrammingTips-2.png)
Why does this SAS program produce an error? proc means data=sashelp.cars mean median min max; by origin; run; It's because SASHELP.CARS is a SAS data set, and SAS data sets observations are stored and processed sequentially, and a BY group operation requires that the observations are already grouped and sorted
![Viewing SAS catalogs from SAS Enterprise Guide](https://blogs.sas.com/content/sasdummy/files/2017/01/ProgrammingTips-1.png)
SAS catalogs have been around for a long time. Not quite as long as the Sears or L.L. Bean catalogs, but SAS customers have used catalogs to store and retrieve content for many years. A SAS catalog is a special type of SAS file that acts as a container, like
![Keeping historical versions of output from SAS Enterprise Guide](https://blogs.sas.com/content/sasdummy/files/2017/01/ProgrammingTips-1.png)
This is the topic of an 8-minute video tip from SAS Education. What's great about this tip: not only does it show you how to keep historical versions of reports and data that you create in your projects, but it also provides a nice example of cross-tab reporting in SAS
![In the year 9999...](https://blogs.sas.com/content/sasdummy/files/2017/02/ProgrammingTips-3.png)
...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