Click on any hyperlinked topic for an abstract | |
---|---|
12:15 - 1:00 | Registration* |
1:00 - 1:10 | President's opening remarks |
1:10 - 2:00 |
An Update on SAS and ODBC Jennifer Price Spectrum Concepts Consulting |
2:00 - 2:15 | Breakout - Refreshments * |
2:15 - 3:05 |
There's No Such Thing as Normal Clinical Trials Data, or Is There? Daphne Ewing Synteract, Inc. |
3:05 - 3:20 | Breakout - Refreshments * |
3:20 - 3:35 | Open Forum, Business Issues |
3:35 - 4:25 |
CREATING, MAINTAINING AND ACCESSING SAS MACRO LIBRARIES
Michael A. Walega Covance, Inc. |
4:25 - 4:30 | MBCR (Mercifully Brief Closing Remarks) |
Light refreshments will be served during breaks * The local office of the SAS Institute has promised us a demonstration showing some of the new features of SAS Release 7. This will occur during the meeting registration and breakout sessions. |
You are invited to join the speakers and the PhilaSUG Executive Committee for dinner at a nearby restaurant at the conclusion of the meeting. The location will be announced at the meeting.
Papers |
An Update on SAS and ODBC Jennifer Price Spectrum Concepts Consulting
An Update on SAS and ODBC
BIOGRAPHY:
|
Daphne Ewing Synteract, Inc.
ABSTRACT:
This paper will discuss data normalization and what it means along with the effects it has on SAS? programs used to list and summarize clinical trials data. Side by side examples of programs and output from standard data structures versus normalized data structures will provide proof of the importance of normalization.
BIOGRAPHY:
|
Michael A. Walega Covance, Inc. So you've written the World's Greatest SAS Macro program. Now, how do other users get access to it? Copy it to their accounts you say? Then how do you keep the other SAS programming gurus from tweaking your program such that one month later you don't recognize any of the code? That is, if they can read your code. Did you follow good programming practices (lots of white space and documentation)? The ability to reuse code in the form of SAS Macro programs is only as good as the infrastructure that supports these programs. A common program warehouse, the SAS Macro Library, can provide the necessary environment for your macro programs. Macro programs that are designed for multi-user access are stored here; by limiting accessibility to the library, version control really is version control. Good programming practices can be enforced. Development of sufficiently generic code can be controlled. This paper describes the steps necessary to develop and maintain the infrastructure necessary for SAS Macro Libraries to be useful and successful. This includes the systems aspect of the Macro Library (location, access) as well as the developmental aspect of the Macro programs (documentation, validation).
BIOGRAPHY:
|
Last Update: 7:19PM 1/24/99