.

Importing Excel Files Into SAS Using DDE What in the world is DDE and why use it? Good question... DDE is “Dynamic Data Exchange” and is a method of accessing data from one MS-Windows application by another. As a SAS user, you can use DDE within a DATA step to import data into SAS and export data from SAS. Using DDE involves SAS code and statements that other MS-Windows applications understand. But, why bother with DDE when other methods are available? What about the IMPORT and EXPORT procedures? Or, Open Database Connectivity (ODBC)? How about SAS Enterprise Guide? These alternatives are useful under the right conditions. For example, the PROC IMPORT and PROC EXPORT are simple to use, but are limited in the way you can define your data and these procedures require you license SAS/ACCESS For PC Formats. Bummer. ODBC is also simple to use, but importing data into SAS using ODBC requires you license SAS/ACCESS For ODBC. Bummer again. And, the new Excel LIBNAME engine? Oh, that also req...

I am not sure what other fellow SAS Programmers think about SAS Graphs, but I think they are easy to generate than tables…. I was amazed by how easy it was to get more than 1-2 graphs in single page. While surfing on the net, I found a nice SUGI paper which deals with the ways of putting multiple graphs in one single page. This paper provides 3 different methods (PROC GREPLAY, the Data Step Graphics Interface (DSGI), and ODS LAYOUT) to put multiple figures on a one single page. Multiple Graphs on One Page Using SAS/GRAPH® V9

20 SAS Macros Tips in 30 Minutes

Need to convert SDTM data to ADaM data? Here's (Clinplus Report) Introduction If you have you been wondering how you can effectively meet the clinical data study standards set out by the Clinical Data Interchange Standards Consortium (CDISC) specifically with regards to the Study Data Tabulation Module (SDTM) and the Analysis Data Model (ADaM) our data conversion and reporting tool may be the solution you are looking for to generate all of your safety tables and listings and provide supporting documentation in a validated, standardized ADaM compliant manner. A Taste of SDTM in Real Time Do we need to create ADaM dataset for each SDTM dataset? By Jack Shostak: You do not need to create an analysis dataset for every SDTM domain. The SDTM files can be used as-is (and probably with support from ADSL for key analysis variables) for statistical analysis if you can get away with that. The idea with analysis datasets and ADaM is that ADaM datasets are value added. ADaM...

This paper presents a set of programming guidelines and conventions that can be considered in developing code to ensure that it is clear, efficient, transferable and maintainable. These are not hard and fast rules but they are generally accepted good programming practices. These techniques can be used in all types of SAS® programs, on all platforms, by beginners and experts alike. SAS ® PROGRAM EFFICIENCY FOR BEGINNERS Guidelines for Coding of SAS® Programs

2009 November - Looping the loop with DO loops October - The Use and Abuse of the NODUPKEY option in the SORT Procedure September - Comparing all datasets in one directory against all the datasets in a second dataset, using CALL EXECUTE August - Selecting data for a particular month July - I am missing a '0' in front of my day value, can SAS still read it okay? (or can SAS read a text date of '6JUN2009' correctly) June - Prefixing a value with '+' or '-' May - Why use dataset variable labels? April - More on using a FORMAT to merge data March - Delete all datasets in a library, except ... February - Getting rid of the message "NOTE: BASE data set does not exist. DATA file is being copied to BASE file." January - SUM(OF variables) 2008 December - Making a copy of a SAS dataset, Part 2 November - How would I set only character or numeric variables of an observation to missing? October - Making a copy of a SAS dataset, ...

A many-to-many match-merge is more complicated. When we try to do many-to-many merge that means both the data sets have multiple occurrences of BY variable values. Simple match-merge the two data sets using the BY statement is never OK… Because when we do, we get the following note in the log. "NOTE: MERGE statement has more than one data set with repeats of BY values." SAS Programmer always tries to avoid this message in the log file….because this message means that the resulting data set is probably not what we expected. Don’t be afraid that there is no way… you can do many-to-many merge using data step. A well known SAS Expert David Franklin points out a way to do many-to-many merge Many Thanks David! (Read his original post here ) NS8PO19P The Fundamentals of MERGE