Table of contents:

• Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27)
• CI and SE bars (15 messages)
• Calculating Readmissions (9 messages)
• Can one recover a deleted log? (5 messages)
• FW: Re: PROC EXPLODE and semicolons
• Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (24 messages)
• Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (5 messages)
• HTML tags in ODS HTML files
• How does SAS Handle This? (4 messages)
• How to manipulate data (5 messages)
• IBNR / Chain Ladder
• Is it sorted? Are there performance benefits? (15 messages)
• Least and most helpful SAS error message (7 messages)
• Logistic Regression Intercept Pr>Chisq (3 messages)
• Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (6 messages)
• Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (12 messages)
• Macro Reading Filename (8 messages)
• Maximum Size for Character Variables? (2 messages)
• Misc. SAS Gplot/Greplay Questions (7 messages)
• Multiple Semicolons (was PROC EXPLODE and semicolons) (19 messages)
• NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (4 messages)
• ODS HTML Question
• ODS PDF (5 messages)
• PROC EXPLODE and semicolons (3 messages)
• PROC FORMAT with dates (3 messages)
• PROC GCHART: Explicitly control the ordering of group variables (4 messages)
• Prevent procedure output from beginning on a new page (5 messages)
• Proc SQL BETWEEN statement is less efficient? (8 messages)
• Proc sql pass through, meta data, proc contents? (6 messages)
• RTF Output (3 messages)
• Recovering a deleted log (2 messages)
• SAS Unix (4 messages)
• SAS on iPad? (6 messages)
• SAS v9.3 ship date
• SQL Full Join Problem
• Sas File Locking (6 messages)
• Sign after the numbers (9 messages)
• The d in w.d informat (6 messages)
• Unix SAS (11 messages)
• Your webmail quota has exceeded the set quota which is 20GB.
• blanks in html output (4 messages)
• finding gaps given date ranges and covered date ranges (2 messages)
• gplot question color of reference line (2 messages)
• help with matching without replacement (4 messages)
• how to show variables with its full infomation in viewtable (2 messages)
• markov transition model with binary response
• modulen: where does SAS look? (5 messages)
• partitioning a variable (11 messages)
• proc mixed 4-levels (2 messages)
• relative risk with proc freq multiple variables
• subject terms in the repeated measures mixed model, split plot with RCBD
• teaching SAS (10 messages)
• the compute block in proc report (7 messages)
• unsubscribe sas-l
• xlm to SAS dataset (5 messages)

1. Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27)
   • Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27) (14 lines)
     From: Carol Olson <Carol.Olson@MEREDITH.COM>

2. CI and SE bars
   • CI and SE bars (23 lines)
     From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>
   • Re: CI and SE bars (43 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: CI and SE bars (65 lines)
     From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>
   • Re: CI and SE bars (62 lines)
     From: Nat Wooding <nathani@VERIZON.NET>
   • Re: CI and SE bars (90 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: CI and SE bars (56 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>
   • Re: CI and SE bars (76 lines)
     From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>
   • Re: CI and SE bars (40 lines)
     From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
   • Re: CI and SE bars (29 lines)
     From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
   • Re: CI and SE bars (22 lines)
     From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
   • Re: CI and SE bars (39 lines)
     From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>
   • Re: CI and SE bars (89 lines)
     From: Susan Durham <sdurham@BIOLOGY.USU.EDU>
   • Re: CI and SE bars (35 lines)
     From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
   • Re: CI and SE bars (48 lines)
     From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>
   • Re: CI and SE bars (26 lines)
     From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

3. Calculating Readmissions
   • Re: Calculating Readmissions (129 lines)
     From: Shelley Perritt <hims.sperritt@SYMPATICO.CA>
   • Re: Calculating Readmissions (26 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Calculating Readmissions (54 lines)
     From: HIMS <hims.sperritt@SYMPATICO.CA>
   • Re: Calculating Readmissions (71 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Calculating Readmissions (98 lines)
     From: HIMS <hims.sperritt@SYMPATICO.CA>
   • Re: Calculating Readmissions (206 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Calculating Readmissions (221 lines)
     From: HIMS <hims.sperritt@SYMPATICO.CA>
   • Re: Calculating Readmissions (61 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Calculating Readmissions (81 lines)
     From: HIMS <hims.sperritt@SYMPATICO.CA>

4. Can one recover a deleted log?
   • Can one recover a deleted log? (15 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Can one recover a deleted log? (30 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: Can one recover a deleted log? (36 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Can one recover a deleted log? (65 lines)
     From: Kirby, Ted <ted.kirby@LEWIN.COM>
   • Re: Can one recover a deleted log? (36 lines)
     From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

5. FW: Re: PROC EXPLODE and semicolons
   • FW: Re: PROC EXPLODE and semicolons (43 lines)
     From: Kirby, Ted <ted.kirby@LEWIN.COM>

6. Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature"
   • Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines)
     From: Dale McLerran <stringplayer_2@YAHOO.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines)
     From: T J <tj_noreply@YAHOO.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines)
     From: Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (73 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (24 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines)
     From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines)
     From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines)
     From: Nat Wooding <nathani@VERIZON.NET>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines)
     From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines)
     From: T J <tj_noreply@YAHOO.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (43 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines)
     From: Nat Wooding <nathani@VERIZON.NET>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines)
     From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines)
     From: T J <tj_noreply@YAHOO.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines)
     From: Nat Wooding <nathani@VERIZON.NET>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines)
     From: Dale McLerran <stringplayer_2@YAHOO.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines)
     From: T J <tj_noreply@YAHOO.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines)
     From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines)
     From: T J <tj_noreply@YAHOO.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines)
     From: Dale McLerran <stringplayer_2@YAHOO.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines)
     From: Kirby, Ted <ted.kirby@LEWIN.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (98 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines)
     From: Nat Wooding <nathani@VERIZON.NET>

7. Fun With SAS - My Vote for Oddest SAS Programming Language "Feature"
   • Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines)
     From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
   • Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (48 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines)
     From: Tom Robinson <barefootguru@GMAIL.COM>
   • Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines)
     From: Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>
   • Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines)
     From: Philip Rack <PhilRack@MINEQUEST.COM>

8. HTML tags in ODS HTML files
   • HTML tags in ODS HTML files (46 lines)
     From: Viel, Kevin <kviel@SJHA.ORG>

9. How does SAS Handle This?
   • Re: How does SAS Handle This? (48 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: How does SAS Handle This? (160 lines)
     From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
   • Re: How does SAS Handle This? (178 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: How does SAS Handle This? (95 lines)
     From: Søren Lassen <s.lassen@POST.TELE.DK>

10. How to manipulate data
    • How to manipulate data (21 lines)
      From: vivian v <v.vivian3@GMAIL.COM>
    • Re: How to manipulate data (35 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: How to manipulate data (45 lines)
      From: vivian v <v.vivian3@GMAIL.COM>
    • Re: How to manipulate data (55 lines)
      From: vivian v <v.vivian3@GMAIL.COM>
    • Re: How to manipulate data (72 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

11. IBNR / Chain Ladder
    • Re: IBNR / Chain Ladder (15 lines)
      From: Eric Hoogenboom <erichoogenboom@YAHOO.COM>

12. Is it sorted? Are there performance benefits?
    • Is it sorted? Are there performance benefits? (44 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Is it sorted? Are there performance benefits? (75 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Is it sorted? Are there performance benefits? (122 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Is it sorted? Are there performance benefits? (138 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Is it sorted? Are there performance benefits? (123 lines)
      From: Mike Zdeb <msz03@ALBANY.EDU>
    • Re: Is it sorted? Are there performance benefits? (151 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Is it sorted? Are there performance benefits? (111 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Is it sorted? Are there performance benefits? (150 lines)
      From: Mike Zdeb <msz03@ALBANY.EDU>
    • Re: Is it sorted? Are there performance benefits? (230 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Is it sorted? Are there performance benefits? (176 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Is it sorted? Are there performance benefits? (190 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Is it sorted? Are there performance benefits? (202 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Is it sorted? Are there performance benefits? (202 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is it sorted? Are there performance benefits? (307 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Is it sorted? Are there performance benefits? (338 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

13. Least and most helpful SAS error message
    • Least and most helpful SAS error message (20 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Least and most helpful SAS error message (33 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Least and most helpful SAS error message (37 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Least and most helpful SAS error message (45 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Least and most helpful SAS error message (134 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Least and most helpful SAS error message (41 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Least and most helpful SAS error message (96 lines)
      From: Robin R High <rhigh@UNMC.EDU>

14. Logistic Regression Intercept Pr>Chisq
    • Logistic Regression Intercept Pr>Chisq (37 lines)
      From: Tanmoy Mukherjee <tkmcornell@YAHOO.COM>
    • Re: Logistic Regression Intercept Pr>Chisq (78 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: Logistic Regression Intercept Pr>Chisq (48 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

15. Love With SAS - My Vote for my favorite SAS Programming Language "Feature"
    • Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

16. Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma
    • Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>
    • Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>
    • Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
    • Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>
    • Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>

17. Macro Reading Filename
    • Macro Reading Filename (39 lines)
      From: Brian Trautman <btrautman84@GMAIL.COM>
    • Re: Macro Reading Filename (57 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Macro Reading Filename (71 lines)
      From: Brian Trautman <btrautman84@GMAIL.COM>
    • Re: Macro Reading Filename (131 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Macro Reading Filename (91 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Macro Reading Filename (116 lines)
      From: Brian Trautman <btrautman84@GMAIL.COM>
    • Re: Macro Reading Filename (92 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: Macro Reading Filename (138 lines)
      From: Brian Trautman <btrautman84@GMAIL.COM>

18. Maximum Size for Character Variables?
    • Maximum Size for Character Variables? (96 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: Maximum Size for Character Variables? (98 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

19. Misc. SAS Gplot/Greplay Questions
    • Misc. SAS Gplot/Greplay Questions (201 lines)
      From: Peter the SAS Hack <phlarsen@YAHOO.COM>
    • Re: Misc. SAS Gplot/Greplay Questions (234 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Misc. SAS Gplot/Greplay Questions (266 lines)
      From: Peter <phlarsen@YAHOO.COM>
    • Re: Misc. SAS Gplot/Greplay Questions (303 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Misc. SAS Gplot/Greplay Questions (364 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Misc. SAS Gplot/Greplay Questions (392 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Misc. SAS Gplot/Greplay Questions (408 lines)
      From: Peter <phlarsen@YAHOO.COM>

20. Multiple Semicolons (was PROC EXPLODE and semicolons)
    • Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (101 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (160 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines)
      From: Chris Brooks <Chris.Brooks@ONS.GOV.UK>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines)
      From: Chris Brooks <Chris.Brooks@ONS.GOV.UK>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (69 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

21. NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma)
    • NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>

22. ODS HTML Question
    • Re: ODS HTML Question (67 lines)
      From: John Birken <zbq5@CDC.GOV>

23. ODS PDF
    • ODS PDF (14 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: ODS PDF (30 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: ODS PDF (42 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: ODS PDF (57 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: ODS PDF (68 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>

24. PROC EXPLODE and semicolons
    • PROC EXPLODE and semicolons (64 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: PROC EXPLODE and semicolons (21 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: PROC EXPLODE and semicolons (83 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

25. PROC FORMAT with dates
    • PROC FORMAT with dates (62 lines)
      From: Paul Bartells <paul.bartells@TARGETBASE.COM>
    • Re: PROC FORMAT with dates (75 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: PROC FORMAT with dates (102 lines)
      From: Bartells, Paul <Paul.Bartells@TARGETBASE.COM>

26. PROC GCHART: Explicitly control the ordering of group variables
    • PROC GCHART: Explicitly control the ordering of group variables (124 lines)
      From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>
    • Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines)
      From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>

27. Prevent procedure output from beginning on a new page
    • Prevent procedure output from beginning on a new page (85 lines)
      From: Scott Bass <sas_l_739@YAHOO.COM.AU>
    • Re: Prevent procedure output from beginning on a new page (39 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Prevent procedure output from beginning on a new page (37 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Prevent procedure output from beginning on a new page (18 lines)
      From: Scott Bass <sas_l_739@YAHOO.COM.AU>
    • Re: Prevent procedure output from beginning on a new page (46 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

28. Proc SQL BETWEEN statement is less efficient?
    • Proc SQL BETWEEN statement is less efficient? (27 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: Proc SQL BETWEEN statement is less efficient? (55 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
    • Re: Proc SQL BETWEEN statement is less efficient? (41 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Proc SQL BETWEEN statement is less efficient? (50 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Proc SQL BETWEEN statement is less efficient? (61 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Proc SQL BETWEEN statement is less efficient? (47 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Proc SQL BETWEEN statement is less efficient? (73 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: Proc SQL BETWEEN statement is less efficient? (75 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

29. Proc sql pass through, meta data, proc contents?
    • Proc sql pass through, meta data, proc contents? (25 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Proc sql pass through, meta data, proc contents? (45 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Proc sql pass through, meta data, proc contents? (54 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Proc sql pass through, meta data, proc contents? (32 lines)
      From: Huang, Ya <Ya.Huang@AMYLIN.COM>
    • Re: Proc sql pass through, meta data, proc contents? (124 lines)
      From: Carol Bristow <Carol.Bristow@DPRA.COM>
    • Re: Proc sql pass through, meta data, proc contents? (67 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

30. RTF Output
    • RTF Output (36 lines)
      From: James Algina <algina@UFL.EDU>
    • Re: RTF Output (46 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: RTF Output (64 lines)
      From: Paul Hamilton <pdhamilton1@COMCAST.NET>

31. Recovering a deleted log
    • Recovering a deleted log (22 lines)
      From: Braun, Joseph M. <joebraun@PURDUE.EDU>
    • Re: Recovering a deleted log (33 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

32. SAS Unix
    • SAS Unix (15 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: SAS Unix (61 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: SAS Unix (69 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: SAS Unix (119 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

33. SAS on iPad?
    • SAS on iPad? (22 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: SAS on iPad? (32 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: SAS on iPad? (22 lines)
      From: Jeremy Miles <jeremy.miles@GMAIL.COM>
    • Re: SAS on iPad? (40 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: SAS on iPad? (50 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: SAS on iPad? (58 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

34. SAS v9.3 ship date
    • SAS v9.3 ship date (35 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

35. SQL Full Join Problem
    • SQL Full Join Problem (106 lines)
      From: Craig Johnson <cjohns38@GMAIL.COM>

36. Sas File Locking
    • Sas File Locking (63 lines)
      From: Allen Ziegenfus <aziegenfus@GMAIL.COM>
    • Re: Sas File Locking (50 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Sas File Locking (58 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Sas File Locking (68 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Sas File Locking (33 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Sas File Locking (57 lines)
      From: Reeza K <fkhurshed@HOTMAIL.COM>

37. Sign after the numbers
    • Sign after the numbers (27 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Sign after the numbers (58 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Sign after the numbers (63 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Sign after the numbers (67 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Sign after the numbers (80 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Sign after the numbers (99 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Sign after the numbers (107 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Sign after the numbers (117 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Sign after the numbers (128 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

38. The d in w.d informat
    • The d in w.d informat (98 lines)
      From: Stehle, James <James.Stehle@BEA.GOV>
    • Re: The d in w.d informat (126 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: The d in w.d informat (35 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: The d in w.d informat (113 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: The d in w.d informat (146 lines)
      From: Stehle, James <James.Stehle@BEA.GOV>
    • Re: The d in w.d informat (185 lines)
      From: Mike Zdeb <msz03@ALBANY.EDU>

39. Unix SAS
    • Unix SAS (15 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: Unix SAS (41 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Unix SAS (49 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: Unix SAS (48 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Unix SAS (85 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Unix SAS (37 lines)
      From: Jonas Bilenas <jonas.bilenas@CHASE.COM>
    • Re: Unix SAS (103 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: Unix SAS (44 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Unix SAS (56 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: Unix SAS (128 lines)
      From: Duck-Hye Yang <dyang@CHAPINHALL.ORG>
    • Re: Unix SAS (91 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

40. Your webmail quota has exceeded the set quota which is 20GB.
    • Your webmail quota has exceeded the set quota which is 20GB. (28 lines)
      From: Jamil M Ibrahim <jibrahim@UMC.EDU>

41. blanks in html output
    • blanks in html output (29 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: blanks in html output (50 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: blanks in html output (73 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: blanks in html output (20 lines)
      From: Ksharp <xiakeshan@YAHOO.COM.CN>

42. finding gaps given date ranges and covered date ranges
    • finding gaps given date ranges and covered date ranges (33 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: finding gaps given date ranges and covered date ranges (121 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

43. gplot question color of reference line
    • gplot question color of reference line (22 lines)
      From: df ss <tggsun@YAHOO.COM>
    • Re: gplot question color of reference line (35 lines)
      From: Akshaya <akshaya.nathilvar@GMAIL.COM>

44. help with matching without replacement
    • help with matching without replacement (33 lines)
      From: Tracy Li <lisiqi77@YAHOO.COM>
    • Re: help with matching without replacement (49 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: help with matching without replacement (63 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: help with matching without replacement (77 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

45. how to show variables with its full infomation in viewtable
    • how to show variables with its full infomation in viewtable (16 lines)
      From: Karen L <hl2493@YAHOO.COM>
    • Re: how to show variables with its full infomation in viewtable (22 lines)
      From: Karen L <hl2493@YAHOO.COM>

46. markov transition model with binary response
    • markov transition model with binary response (22 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>

47. modulen: where does SAS look?
    • modulen: where does SAS look? (59 lines)
      From: James Oliver <james.oliver@STATE.OR.US>
    • Re: modulen: where does SAS look? (15 lines)
      From: James Oliver <james.oliver@STATE.OR.US>
    • Re: modulen: where does SAS look? (96 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: modulen: where does SAS look? (75 lines)
      From: Allen Ziegenfus <aziegenfus@GMAIL.COM>
    • Re: modulen: where does SAS look? (39 lines)
      From: James Oliver <james.oliver@STATE.OR.US>

48. partitioning a variable
    • partitioning a variable (18 lines)
      From: Karen L <hl2493@YAHOO.COM>
    • Re: partitioning a variable (56 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: partitioning a variable (42 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: partitioning a variable (49 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: partitioning a variable (30 lines)
      From: Karen L <hl2493@YAHOO.COM>
    • Re: partitioning a variable (101 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: partitioning a variable (91 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: partitioning a variable (34 lines)
      From: Karen L <hl2493@YAHOO.COM>
    • Re: partitioning a variable (38 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: partitioning a variable (43 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: partitioning a variable (65 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

49. proc mixed 4-levels
    • proc mixed 4-levels (50 lines)
      From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>
    • Re: proc mixed 4-levels (59 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>

50. relative risk with proc freq multiple variables
    • relative risk with proc freq multiple variables (34 lines)
      From: Amy Krueger <amyk4422@GMAIL.COM>

51. subject terms in the repeated measures mixed model, split plot with RCBD
    • subject terms in the repeated measures mixed model, split plot with RCBD (78 lines)
      From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

52. teaching SAS
    • teaching SAS (18 lines)
      From: Ali Zanaty <zanaty2005@YAHOO.COM>
    • Re: teaching SAS (45 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: teaching SAS (53 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: teaching SAS (95 lines)
      From: Mike Zdeb <msz03@ALBANY.EDU>
    • Re: teaching SAS (78 lines)
      From: Ali Zanaty <zanaty2005@YAHOO.COM>
    • Re: teaching SAS (109 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: teaching SAS (59 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: teaching SAS (68 lines)
      From: Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>
    • Re: teaching SAS (47 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: teaching SAS (78 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

53. the compute block in proc report
    • the compute block in proc report (33 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: the compute block in proc report (67 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: the compute block in proc report (113 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: the compute block in proc report (119 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: the compute block in proc report (47 lines)
      From: Tom Robinson <barefootguru@GMAIL.COM>
    • Re: the compute block in proc report (77 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: the compute block in proc report (120 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

54. unsubscribe sas-l
    • unsubscribe sas-l (1040 lines)
      From: Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>

55. xlm to SAS dataset
    • xlm to SAS dataset (17 lines)
      From: Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>
    • Re: xlm to SAS dataset (23 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: xlm to SAS dataset (54 lines)
      From: Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>
    • Re: xlm to SAS dataset (46 lines)
      From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>
    • Re: xlm to SAS dataset (64 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>