LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Sort by authorSort by posting dateSort by topic[Separator]Chronological orderMost recent first[Separator]Show authorHide author[Separator]Back to main SAS-L pageJoin or leave SAS-L (or change settings)Search
SAS-L archives – January 2011, week 1

  1. Re: How does SAS Handle This? (48 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  2. Re: How does SAS Handle This? (160 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  3. Re: How does SAS Handle This? (178 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  4. Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines)
    From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>

  5. Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (48 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  6. Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

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

  8. Re: How does SAS Handle This? (95 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  9. Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  10. PROC FORMAT with dates (62 lines)
    From: Paul Bartells <paul.bartells@TARGETBASE.COM>

  11. Re: PROC FORMAT with dates (75 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  12. Re: PROC FORMAT with dates (102 lines)
    From: Bartells, Paul <Paul.Bartells@TARGETBASE.COM>

  13. Macro Reading Filename (39 lines)
    From: Brian Trautman <btrautman84@GMAIL.COM>

  14. Re: Macro Reading Filename (57 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  15. Proc sql pass through, meta data, proc contents? (25 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  16. Re: Proc sql pass through, meta data, proc contents? (45 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  17. Re: Proc sql pass through, meta data, proc contents? (54 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  18. Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines)
    From: Tom Robinson <barefootguru@GMAIL.COM>

  19. Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines)
    From: Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>

  20. Re: Proc sql pass through, meta data, proc contents? (32 lines)
    From: Huang, Ya <Ya.Huang@AMYLIN.COM>

  21. Re: Proc sql pass through, meta data, proc contents? (124 lines)
    From: Carol Bristow <Carol.Bristow@DPRA.COM>

  22. Re: Macro Reading Filename (71 lines)
    From: Brian Trautman <btrautman84@GMAIL.COM>

  23. the compute block in proc report (33 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  24. PROC EXPLODE and semicolons (64 lines)
    From: Kirby, Ted <ted.kirby@LEWIN.COM>

  25. Re: Macro Reading Filename (131 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  26. Re: the compute block in proc report (67 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  27. Re: Macro Reading Filename (91 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  28. Re: the compute block in proc report (113 lines)
    From: Kirby, Ted <ted.kirby@LEWIN.COM>

  29. Re: Macro Reading Filename (116 lines)
    From: Brian Trautman <btrautman84@GMAIL.COM>

  30. Re: the compute block in proc report (119 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  31. Prevent procedure output from beginning on a new page (85 lines)
    From: Scott Bass <sas_l_739@YAHOO.COM.AU>

  32. Re: Macro Reading Filename (92 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

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

  34. Re: the compute block in proc report (47 lines)
    From: Tom Robinson <barefootguru@GMAIL.COM>

  35. Re: Prevent procedure output from beginning on a new page (39 lines)
    From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

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

  37. Re: Prevent procedure output from beginning on a new page (37 lines)
    From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

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

  39. Re: PROC EXPLODE and semicolons (21 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  40. Re: PROC EXPLODE and semicolons (83 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  41. Sign after the numbers (27 lines)
    From: Chang Chung <chang_y_chung@HOTMAIL.COM>

  42. Re: Sign after the numbers (58 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  43. Re: Sign after the numbers (63 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  44. Re: the compute block in proc report (77 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  45. Re: Sign after the numbers (67 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  46. Re: Sign after the numbers (80 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  47. Re: Sign after the numbers (99 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  48. Re: Sign after the numbers (107 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  49. Re: Sign after the numbers (117 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

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

  51. Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines)
    From: Kirby, Ted <ted.kirby@LEWIN.COM>

  52. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines)
    From: Chang Chung <chang_y_chung@HOTMAIL.COM>

  53. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (101 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  54. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  55. Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines)
    From: Philip Rack <PhilRack@MINEQUEST.COM>

  56. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  57. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  58. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  59. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  60. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  61. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (160 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  62. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  63. Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  64. Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines)
    From: Chang Chung <chang_y_chung@HOTMAIL.COM>

  65. Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines)
    From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

  66. Re: Sign after the numbers (128 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  67. Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  68. Re: the compute block in proc report (120 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  69. Is it sorted? Are there performance benefits? (44 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  70. Re: Is it sorted? Are there performance benefits? (75 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  71. Re: Is it sorted? Are there performance benefits? (122 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  72. Re: Is it sorted? Are there performance benefits? (138 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  73. Re: Is it sorted? Are there performance benefits? (123 lines)
    From: Mike Zdeb <msz03@ALBANY.EDU>

  74. Re: Is it sorted? Are there performance benefits? (151 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  75. Re: Is it sorted? Are there performance benefits? (111 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  76. Re: Is it sorted? Are there performance benefits? (150 lines)
    From: Mike Zdeb <msz03@ALBANY.EDU>

  77. Re: Is it sorted? Are there performance benefits? (230 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  78. Re: Is it sorted? Are there performance benefits? (176 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  79. Re: Is it sorted? Are there performance benefits? (190 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  80. ODS PDF (14 lines)
    From: John Mike <sasslick@GMAIL.COM>

  81. Re: ODS PDF (30 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  82. Re: Is it sorted? Are there performance benefits? (202 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  83. Re: Is it sorted? Are there performance benefits? (202 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  84. Re: ODS PDF (42 lines)
    From: John Mike <sasslick@GMAIL.COM>

  85. Re: ODS PDF (57 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  86. Re: Is it sorted? Are there performance benefits? (307 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  87. teaching SAS (18 lines)
    From: Ali Zanaty <zanaty2005@YAHOO.COM>

  88. Re: Is it sorted? Are there performance benefits? (338 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  89. Can one recover a deleted log? (15 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  90. Re: Can one recover a deleted log? (30 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  91. Re: Can one recover a deleted log? (36 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  92. Re: ODS PDF (68 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  93. Re: Can one recover a deleted log? (65 lines)
    From: Kirby, Ted <ted.kirby@LEWIN.COM>

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

  95. Re: teaching SAS (45 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  96. Re: Prevent procedure output from beginning on a new page (18 lines)
    From: Scott Bass <sas_l_739@YAHOO.COM.AU>

  97. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines)
    From: Chris Brooks <Chris.Brooks@ONS.GOV.UK>

  98. Re: Prevent procedure output from beginning on a new page (46 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  99. Re: teaching SAS (53 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  100. Re: Can one recover a deleted log? (36 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  101. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  102. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines)
    From: Chris Brooks <Chris.Brooks@ONS.GOV.UK>

  103. Recovering a deleted log (22 lines)
    From: Braun, Joseph M. <joebraun@PURDUE.EDU>

  104. Re: Recovering a deleted log (33 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  105. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  106. Re: teaching SAS (95 lines)
    From: Mike Zdeb <msz03@ALBANY.EDU>

  107. SAS on iPad? (22 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

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

  109. Re: SAS on iPad? (32 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  110. Re: SAS on iPad? (22 lines)
    From: Jeremy Miles <jeremy.miles@GMAIL.COM>

  111. Re: SAS on iPad? (40 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

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

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

  114. Re: SAS on iPad? (50 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

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

  116. blanks in html output (29 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  117. modulen: where does SAS look? (59 lines)
    From: James Oliver <james.oliver@STATE.OR.US>

  118. Re: modulen: where does SAS look? (15 lines)
    From: James Oliver <james.oliver@STATE.OR.US>

  119. Re: blanks in html output (50 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  120. Re: Macro Reading Filename (138 lines)
    From: Brian Trautman <btrautman84@GMAIL.COM>

  121. Misc. SAS Gplot/Greplay Questions (201 lines)
    From: Peter the SAS Hack <phlarsen@YAHOO.COM>

  122. Re: SAS on iPad? (58 lines)
    From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

  123. Re: Misc. SAS Gplot/Greplay Questions (234 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  124. Re: blanks in html output (73 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  125. Re: blanks in html output (20 lines)
    From: Ksharp <xiakeshan@YAHOO.COM.CN>

  126. PROC GCHART: Explicitly control the ordering of group variables (124 lines)
    From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>

  127. Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  128. Re: modulen: where does SAS look? (96 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  129. Re: modulen: where does SAS look? (75 lines)
    From: Allen Ziegenfus <aziegenfus@GMAIL.COM>

  130. Re: Proc sql pass through, meta data, proc contents? (67 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  131. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  132. Unix SAS (15 lines)
    From: John Mike <sasslick@GMAIL.COM>

  133. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (69 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  134. Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines)
    From: Jack Clark <jclark@HILLTOP.UMBC.EDU>

  135. Re: Unix SAS (41 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  136. Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  137. Re: Unix SAS (49 lines)
    From: John Mike <sasslick@GMAIL.COM>

  138. Re: Unix SAS (48 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  139. Re: Unix SAS (85 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  140. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  141. partitioning a variable (18 lines)
    From: Karen L <hl2493@YAHOO.COM>

  142. Re: partitioning a variable (56 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  143. Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  144. Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines)
    From: Jack Clark <jclark@HILLTOP.UMBC.EDU>

  145. Re: Unix SAS (37 lines)
    From: Jonas Bilenas <jonas.bilenas@CHASE.COM>

  146. Re: Unix SAS (103 lines)
    From: John Mike <sasslick@GMAIL.COM>

  147. Re: Unix SAS (44 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  148. Re: Unix SAS (56 lines)
    From: John Mike <sasslick@GMAIL.COM>

  149. Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  150. 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>

  151. Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines)
    From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>

  152. Re: partitioning a variable (42 lines)
    From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>

  153. CI and SE bars (23 lines)
    From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

  154. gplot question color of reference line (22 lines)
    From: df ss <tggsun@YAHOO.COM>

  155. Re: gplot question color of reference line (35 lines)
    From: Akshaya <akshaya.nathilvar@GMAIL.COM>

  156. Re: CI and SE bars (43 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  157. Re: Misc. SAS Gplot/Greplay Questions (266 lines)
    From: Peter <phlarsen@YAHOO.COM>

  158. Re: CI and SE bars (65 lines)
    From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

  159. Re: CI and SE bars (62 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  160. Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  161. Re: CI and SE bars (90 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  162. Re: CI and SE bars (56 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  163. Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  164. Re: Misc. SAS Gplot/Greplay Questions (303 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  165. Re: Misc. SAS Gplot/Greplay Questions (364 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  166. 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>

  167. Re: Misc. SAS Gplot/Greplay Questions (392 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  168. Re: Unix SAS (128 lines)
    From: Duck-Hye Yang <dyang@CHAPINHALL.ORG>

  169. Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines)
    From: Jack Clark <jclark@HILLTOP.UMBC.EDU>

  170. Re: Unix SAS (91 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  171. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines)
    From: T J <tj_noreply@YAHOO.COM>

  172. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines)
    From: Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>

  173. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (73 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  174. Re: CI and SE bars (76 lines)
    From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

  175. Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines)
    From: Yu Zhang <zhangyu05@GMAIL.COM>

  176. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (24 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  177. Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines)
    From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>

  178. Re: partitioning a variable (49 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

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

  180. Re: CI and SE bars (40 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  181. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  182. Re: CI and SE bars (29 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  183. Re: CI and SE bars (22 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  184. Re: partitioning a variable (30 lines)
    From: Karen L <hl2493@YAHOO.COM>

  185. Re: partitioning a variable (101 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  186. Re: partitioning a variable (91 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  187. Re: partitioning a variable (34 lines)
    From: Karen L <hl2493@YAHOO.COM>

  188. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  189. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  190. Re: partitioning a variable (38 lines)
    From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>

  191. Re: CI and SE bars (39 lines)
    From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

  192. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines)
    From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>

  193. finding gaps given date ranges and covered date ranges (33 lines)
    From: Chang Chung <chang_y_chung@HOTMAIL.COM>

  194. Re: modulen: where does SAS look? (39 lines)
    From: James Oliver <james.oliver@STATE.OR.US>

  195. help with matching without replacement (33 lines)
    From: Tracy Li <lisiqi77@YAHOO.COM>

  196. Re: help with matching without replacement (49 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  197. Re: CI and SE bars (89 lines)
    From: Susan Durham <sdurham@BIOLOGY.USU.EDU>

  198. Proc SQL BETWEEN statement is less efficient? (27 lines)
    From: Jerry <i89rt5@GMAIL.COM>

  199. Re: help with matching without replacement (63 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  200. Re: Proc SQL BETWEEN statement is less efficient? (55 lines)
    From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>

  201. Re: finding gaps given date ranges and covered date ranges (121 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  202. Re: teaching SAS (78 lines)
    From: Ali Zanaty <zanaty2005@YAHOO.COM>

  203. Re: teaching SAS (109 lines)
    From: Murphy Choy <goladin@GMAIL.COM>

  204. Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines)
    From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

  205. Re: Proc SQL BETWEEN statement is less efficient? (41 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  206. Re: partitioning a variable (43 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  207. Re: Proc SQL BETWEEN statement is less efficient? (50 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  208. Re: CI and SE bars (35 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  209. 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>

  210. 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>

  211. Re: Proc SQL BETWEEN statement is less efficient? (61 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  212. Re: partitioning a variable (65 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  213. Re: Proc SQL BETWEEN statement is less efficient? (47 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  214. 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>

  215. Re: Proc SQL BETWEEN statement is less efficient? (73 lines)
    From: Jerry <i89rt5@GMAIL.COM>

  216. Re: teaching SAS (59 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  217. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines)
    From: T J <tj_noreply@YAHOO.COM>

  218. Re: teaching SAS (68 lines)
    From: Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>

  219. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (43 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  220. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  221. Re: Proc SQL BETWEEN statement is less efficient? (75 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  222. Least and most helpful SAS error message (20 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  223. Re: teaching SAS (47 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  224. Re: Least and most helpful SAS error message (33 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  225. Re: Least and most helpful SAS error message (37 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  226. Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines)
    From: Viel, Kevin <kviel@SJHA.ORG>

  227. Re: Least and most helpful SAS error message (45 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  228. 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>

  229. Re: teaching SAS (78 lines)
    From: Viel, Kevin <kviel@SJHA.ORG>

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

  231. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  232. proc mixed 4-levels (50 lines)
    From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>

  233. Re: help with matching without replacement (77 lines)
    From: Viel, Kevin <kviel@SJHA.ORG>

  234. Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  235. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  236. Re: CI and SE bars (48 lines)
    From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

  237. Re: Least and most helpful SAS error message (134 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  238. Re: CI and SE bars (26 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

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

  240. xlm to SAS dataset (17 lines)
    From: Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>

  241. Re: xlm to SAS dataset (23 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  242. Re: Least and most helpful SAS error message (41 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  243. Re: xlm to SAS dataset (54 lines)
    From: Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>

  244. Re: xlm to SAS dataset (46 lines)
    From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>

  245. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines)
    From: T J <tj_noreply@YAHOO.COM>

  246. Re: xlm to SAS dataset (64 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  247. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  248. Sas File Locking (63 lines)
    From: Allen Ziegenfus <aziegenfus@GMAIL.COM>

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

  250. Re: Calculating Readmissions (129 lines)
    From: Shelley Perritt <hims.sperritt@SYMPATICO.CA>

  251. Re: Sas File Locking (50 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  252. Re: Sas File Locking (58 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  253. Re: Sas File Locking (68 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  254. Re: Misc. SAS Gplot/Greplay Questions (408 lines)
    From: Peter <phlarsen@YAHOO.COM>

  255. Re: Sas File Locking (33 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  256. Re: Calculating Readmissions (26 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  257. Re: Sas File Locking (57 lines)
    From: Reeza K <fkhurshed@HOTMAIL.COM>

  258. SAS Unix (15 lines)
    From: John Mike <sasslick@GMAIL.COM>

  259. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  260. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines)
    From: T J <tj_noreply@YAHOO.COM>

  261. Re: Calculating Readmissions (54 lines)
    From: HIMS <hims.sperritt@SYMPATICO.CA>

  262. Re: Calculating Readmissions (71 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  263. Re: SAS Unix (61 lines)
    From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

  264. Re: proc mixed 4-levels (59 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  265. The d in w.d informat (98 lines)
    From: Stehle, James <James.Stehle@BEA.GOV>

  266. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines)
    From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

  267. Re: Calculating Readmissions (98 lines)
    From: HIMS <hims.sperritt@SYMPATICO.CA>

  268. Re: SAS Unix (69 lines)
    From: John Mike <sasslick@GMAIL.COM>

  269. Re: The d in w.d informat (126 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  270. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines)
    From: T J <tj_noreply@YAHOO.COM>

  271. Re: SAS Unix (119 lines)
    From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

  272. How to manipulate data (21 lines)
    From: vivian v <v.vivian3@GMAIL.COM>

  273. Re: How to manipulate data (35 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  274. Re: How to manipulate data (45 lines)
    From: vivian v <v.vivian3@GMAIL.COM>

  275. Re: How to manipulate data (55 lines)
    From: vivian v <v.vivian3@GMAIL.COM>

  276. Re: Calculating Readmissions (206 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  277. Re: Calculating Readmissions (221 lines)
    From: HIMS <hims.sperritt@SYMPATICO.CA>

  278. RTF Output (36 lines)
    From: James Algina <algina@UFL.EDU>

  279. Re: Calculating Readmissions (61 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  280. Re: RTF Output (46 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  281. Re: RTF Output (64 lines)
    From: Paul Hamilton <pdhamilton1@COMCAST.NET>

  282. Re: Calculating Readmissions (81 lines)
    From: HIMS <hims.sperritt@SYMPATICO.CA>

  283. Re: The d in w.d informat (35 lines)
    From: Chang Chung <chang_y_chung@HOTMAIL.COM>

  284. Re: Least and most helpful SAS error message (96 lines)
    From: Robin R High <rhigh@UNMC.EDU>

  285. Re: The d in w.d informat (113 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  286. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  287. Re: The d in w.d informat (146 lines)
    From: Stehle, James <James.Stehle@BEA.GOV>

  288. Re: The d in w.d informat (185 lines)
    From: Mike Zdeb <msz03@ALBANY.EDU>

  289. Re: How to manipulate data (72 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  290. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines)
    From: Kirby, Ted <ted.kirby@LEWIN.COM>

  291. Logistic Regression Intercept Pr>Chisq (37 lines)
    From: Tanmoy Mukherjee <tkmcornell@YAHOO.COM>

  292. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (98 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  293. Re: Logistic Regression Intercept Pr>Chisq (78 lines)
    From: Robin R High <rhigh@UNMC.EDU>

  294. Maximum Size for Character Variables? (96 lines)
    From: Kirby, Ted <ted.kirby@LEWIN.COM>

  295. Re: Maximum Size for Character Variables? (98 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  296. Re: Logistic Regression Intercept Pr>Chisq (48 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  297. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

Back to the main SAS-L page
listserv.uga.edu
Enterprise Information Technology Services
The University of Georgia
listhelp@uga.edu