Academia.edu no longer supports Internet Explorer.
To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser.
2012
…
7 pages
1 file
In today’s work place, Excel files seem to be the most common files that we deal with. Sometimes we encounter data come in as an excel file with multiple spread sheets. This paper illustrates three approaches as to bring the spread sheets into SAS, where each sheet becomes a SAS dataset. This first method is using DDE (Dynamic Data Exchange). The second method is using a simple macro program to import the multiple spreadsheets one by one. This third method is setting up the excel file as a SAS library and bring in each sheet as a member in the library. The last method is definitely very convenient and easy to use when there are many sheets involved.
2013
In today’s work place, Excel files seem to be the most common files that we deal with. Sometimes we encounter data come in as an Excel file with multiple spread sheets. This paper illustrates three approaches as to bring the spread sheets with SDTM data into SAS, where each sheet becomes a SAS data set. This first method is using DDE (Dynamic Data Exchange). The second method is using a simple macro program to import the multiple spreadsheets one by one. This third method is setting up the Excel file as a SAS library and bring in each sheet as a member in the library. The last method is definitely very convenient and easy to use when there are many sheets involved.
support.sas.com
2005
In a clinical trial, we had sleep data on 90 study participants over 30 one-week study periods. These data were originally stored in Excel® spreadsheets, with separate workbooks for each study period and a separate worksheet within those workbooks for each participant. Additionally complicating matters, not all subjects participated in all study periods, so the number and the “identities” of the worksheets varied among study periods. Thoughtful and systematic naming of workbook files and the worksheets they contained, along with construction of a “control” SAS® data set indicating which people took part in which study periods, facilitated the development of a few fairly simple SAS macros to automate the IMPORTation of more than 500 spreadsheets and the concatenation of these into a single file for statistical analysis. This paper will present these macros, and demonstrate how the “control” dataset was used to create macro variables that were passed as parameters to the macro that re...
2000
Of all the different ways in which the SAS System allows data export into a Microsoft Excel spreadsheet, Dynamic Data Exchange (DDE) is the only technique providing total control over the Excel output. As is often the case however, this high level of control comes at a price ... The DDE formalism can appear quite daunting at times, even downright
International Journal of Computer Applications, 2016
One of the most powerful and dynamic feature of SAS language is Macro facility. The facility reduces the amount of effort required to read and write SAS code. Macro generates the SAS code automatically and enables one to acquire the skill set to become an efficient SAS programmer. The use of macro has prevailed over time and has deprecated the need to write repetitive codes. With the help of this feature one small change can be made to echo throughout the program in no time. Macro presents a uniform and easy approach for manipulation of data. In this research we explain the basic fundamentals of macro facility to generate data-driven programs .Also, how to create and use macro variables and save them for future aspects.
Dynamic Data Exchange (DDE) can be used on the Windows platform to create fully customized MS Excel and MS Word files, all from within a Base SAS program. But it also comes in handy for gathering useful metadata about your Excel files! When automating the reading from, or writing to an Excel workbook, life becomes a lot easier if you have access to certain facts about the workbook you're manipulating. Such as the names of the worksheets it comprises; the type of each worksheet — data, graphics, or macros; the number of rows and columns that are in use on each data-sheet; whether a given column contains numerical, character, or mixed type values; and so forth. In this tutorial we will go through the necessary DDE-movements that allow the extraction of such Excel workbook metadata. Wrapping up, a SAS macro is shown to load these metadata into a SAS data set for easy reference in the manner of a dictionary table. 0 What's Up? The dictionary tables — or rather, views — that co...
2005
The creation of PowerPoint slides with SAS content using DDE in a Base SAS environment has long been considered impossible. Unlike MS Word and MS Excel, the PowerPoint application does not come with a scripting language like WordBasic or the Excel 4 macro language that would allow DDE to talk to it in a client/server fashion. The job can be done, though, by using DDE to Excel as an intermediate agent to pull the strings of PowerPoint. A set of easy SAS macros is introduced to perform a number of basic PowerPoint operations. As a sample application, a SAS catalog of graphs is exported to a stand-alone PowerPoint presentation. No specific technical knowledge is required from the reader, at least not beyond a basic understanding of the SAS macro language. A slight degree of familiarity with DDE to Excel concepts should prove enlightening, though.
Deciding whether to use an Extraction, Transformation and Loading tool on your Business Intelligence project or to use code is normally a much debated topic. Once this decision has been made and you have completed some form of training you should be ready to begin defining you jobs and extracting data into your solution, Correct? Well maybe not, you may want to spend a little time planning your next steps before you start to develop a large number of jobs. The paper outlines the typical steps needed to design your ETL architecture in order to be successful when implementing an ETL tool like SAS® DI Studio.
2011
SAS® programmers are frequently called upon to perform repetitive processes. To deal with repetitive processing the SAS macro is indispensable. If a process calls for utilizing software (for example WinZip®) outside of SAS, it may be hard (but not impossible!) to figure out how to utilize SAS macros. This paper presents a solution to passing SAS macro code through to an external software call by demonstrating how to use macro variables in WINZIP Command Line Interface (CLI) calls within a SAS program. A bonus is the ability to generate a listing of the resulting zip file and output it to an external file within the SAS program, so that processing done in batch can be easily checked. This example is run on a Windows x64 server, but the process can be used on other platforms.
Annales Universitatis Mariae Curie-Sklodowska, sectio M – Balcaniensis et Carpathiensis
ĐẤU TRANH PHẢN BÁC CÁC QUAN ĐIỂM SAI TRÁI, THÙ ĐỊCH TRONG VẤN ĐỀ BIỂN ĐÔNG VÀ CHỦ QUYỀN BIỂN, ĐẢO VIỆT NAM, 2024
Revista Cadernos de Pesquisa da Escola da Cidade, 2020
International Journal of Trade, Economics and Finance, 2014
Christianity in the Maghrib , 2023
Mid-America Journal of Theology, 2023
Revue Francaise de Photogrammetrie et de Teledetection
Medicinski glasnik : official publication of the Medical Association of Zenica-Doboj Canton, Bosnia and Herzegovina, 2016
Nuclear Physics B, 1975
Dental Poster Journal
American Journal of Roentgenology, 1998
Jornal Brasileiro de Patologia e Medicina Laboratorial, 2010
Annals of Geophysics, 2017
JOURNAL OF CLINICAL AND DIAGNOSTIC RESEARCH, 2018