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 – June 2012, week 2

  1. Re: Creating Folder Dynamically in SAS (23 lines)
    From: Michelle Zunnurain <mzunnurain@HDMS.COM>

  2. Re: SQL: joining on closest datetime match (751 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  3. Re: SQL: joining on closest datetime match (712 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  4. Re: SQL: joining on closest datetime match (633 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  5. Re: SQL: joining on closest datetime match (64 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  6. Re: SQL: joining on closest datetime match (636 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  7. Re: SQL: joining on closest datetime match (447 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  8. Re: Graphing GLM Regression Equation Against Dummy Values (121 lines)
    From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>

  9. Re: SQL: joining on closest datetime match (178 lines)
    From: Sigurd W. Hermansen <hermans1@WESTAT.COM>

  10. Re: New Leadership Council for the SAS Community (76 lines)
    From: Joseph Kelley <jkelley@UGA.EDU>

  11. Re: Dates when extracting data from SQL server with PROC SQL (96 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  12. Dates when extracting data from SQL server with PROC SQL (59 lines)
    From: Howard Alper <halper@HEALTH.NYC.GOV>

  13. Re: Graphing GLM Regression Equation Against Dummy Values (104 lines)
    From: Randi Black <randiblack@GMAIL.COM>

  14. Longitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines)
    From: Mirisage Fernando <neilfrnnd@GMAIL.COM>

  15. Re: Graphing GLM Regression Equation Against Dummy Values (28 lines)
    From: Rick Wicklin <Rick.Wicklin@SAS.COM>

  16. Re: SQL: joining on closest datetime match (258 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  17. Re: SQL: joining on closest datetime match (249 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  18. Re: SQL: joining on closest datetime match (507 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  19. Re: Graphing GLM Regression Equation Against Dummy Values (44 lines)
    From: Steve Denham <stevedrd@YAHOO.COM>

  20. Re: Graphing GLM Regression Equation Against Dummy Values (29 lines)
    From: Steve Denham <stevedrd@YAHOO.COM>

  21. Re: SQL: joining on closest datetime match (215 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  22. Re: SQL: joining on closest datetime match (179 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  23. Re: SQL: joining on closest datetime match (164 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  24. Re: Code (25 lines)
    From: Randy Herbison <RandyHerbison@WESTAT.COM>

  25. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  26. Re: Graphing GLM Regression Equation Against Dummy Values (41 lines)
    From: Rick Wicklin <Rick.Wicklin@SAS.COM>

  27. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines)
    From: Joseph Hinson <jwhinson@GMAIL.COM>

  28. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines)
    From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV>

  29. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines)
    From: .. <ajayohri@YAHOO.COM>

  30. Graphing GLM Regression Equation Against Dummy Values (23 lines)
    From: Randi Black <randiblack@GMAIL.COM>

  31. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  32. Re: Code (69 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  33. Re: Code (62 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  34. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines)
    From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM>

  35. Re: Code (33 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  36. Re: Code (46 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  37. Code (13 lines)
    From: Partha Sinha <pnsinha68@GMAIL.COM>

  38. Re: Confidence interval (xbar-2*ybar) (28 lines)
    From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

  39. Re: In() Function (86 lines)
    From: Gabriel Farkas <g.farkas@GMAIL.COM>

  40. Re: In() Function (266 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  41. Re: Creating Folder Dynamically in SAS (102 lines)
    From: Ben Powell <bpowell555@GMAIL.COM>

  42. Re: Conidence interval (xbar-2*ybar) (10 lines)
    From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM>

  43. Re: Conidence interval (xbar-2*ybar) (38 lines)
    From: Steve Denham <stevedrd@YAHOO.COM>

  44. Re: Q: need to nest PDF bookmarks (112 lines)
    From: Roland Berry <rolandberry@HOTMAIL.COM>

  45. Re: SQL: joining on closest datetime match (133 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  46. Conidence interval (xbar-2*ybar) (17 lines)
    From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM>

  47. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines)
    From: Alan Churchill <savian.net@GMAIL.COM>

  48. New trojan going around (12 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  49. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  50. Re: Transpose data using SQL (39 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  51. Re: Datastep memory leak? (286 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  52. Re: Programmtically accessing WRS Reports (55 lines)
    From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM>

  53. Re: Datastep memory leak? (224 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  54. Re: Datastep memory leak? (127 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  55. Re: Transpose data using SQL (28 lines)
    From: Ben <benpub7@YAHOO.COM>

  56. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines)
    From: William W. Viergever <william@VIERGEVER.NET>

  57. Re: Datastep memory leak? (422 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  58. Re: Creating Folder Dynamically in SAS (79 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  59. PROC MIanalyze and Descriptive Statistics Question (91 lines)
    From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV>

  60. Re: Creating Folder Dynamically in SAS (64 lines)
    From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM>

  61. Re: Programmtically accessing WRS Reports (65 lines)
    From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

  62. Re: Transpose data using SQL (83 lines)
    From: Sigurd W. Hermansen <hermans1@WESTAT.COM>

  63. An Interesting (I think) PROC MIanalyze Question (90 lines)
    From: Malcolm Jazzbeau <jazzlover111@HOTMAIL.COM>

  64. Re: joining on closest datetime match (73 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  65. Re: Transpose data using SQL (21 lines)
    From: Ben <benpub7@YAHOO.COM>

  66. Re: SQL: joining on closest datetime match (97 lines)
    From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

  67. Re: New Leadership Council for the SAS Community (89 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  68. Re: SQL: joining on closest datetime match (60 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  69. Re: Programmtically accessing WRS Reports (50 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  70. Re: Transpose data using SQL (66 lines)
    From: Ben <benpub7@YAHOO.COM>

  71. Re: Programmtically accessing WRS Reports (38 lines)
    From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

  72. Re: In() Function (268 lines)
    From: Zdeb, Michael S <mzdeb@ALBANY.EDU>

  73. Re: SQL: joining on closest datetime match (93 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  74. Re: SQL: joining on closest datetime match (63 lines)
    From: Sigurd W. Hermansen <hermans1@WESTAT.COM>

  75. Re: joining on closest datetime match (84 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  76. Re: In() Function (214 lines)
    From: Paul Dorfman <sashole@BELLSOUTH.NET>

  77. Re: A couple of SAS efficiency questions (133 lines)
    From: DUELL, BOB <bd9439@ATT.COM>

  78. Re: Transpose data using SQL (51 lines)
    From: Sigurd W. Hermansen <hermans1@WESTAT.COM>

  79. Re: Transpose data using SQL (39 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  80. Re: Datastep memory leak? (431 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  81. Re: SQL: joining on closest datetime match (79 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  82. Re: Transpose data using SQL (28 lines)
    From: Ben <benpub7@YAHOO.COM>

  83. Re: SQL: joining on closest datetime match (44 lines)
    From: oloolo <dynamicpanel@YAHOO.COM>

  84. Re: Datastep memory leak? (390 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  85. Re: Transpose data using SQL (32 lines)
    From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV>

  86. SQL: joining on closest datetime match (37 lines)
    From: Kathleen Askland <k.askland@GMAIL.COM>

  87. Programmtically accessing WRS Reports (21 lines)
    From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM>

  88. Re: Transpose data using SQL (104 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  89. Re: Transpose data using SQL (24 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

  90. Re: Transpose data using SQL (14 lines)
    From: Ben <benpub7@YAHOO.COM>

  91. Re: Transpose data using SQL (175 lines)
    From: Ben <benpub7@YAHOO.COM>

  92. Re: Transpose data using SQL (28 lines)
    From: Ben <benpub7@YAHOO.COM>

  93. Re: Transpose data using SQL (9 lines)
    From: Joseph Hinson <jwhinson@GMAIL.COM>

  94. Re: Transpose data using SQL (167 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  95. Re: Transpose data using SQL (154 lines)
    From: Ben <benpub7@YAHOO.COM>

  96. Re: New Leadership Council for the SAS Community (89 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  97. Re: Transpose data using SQL (24 lines)
    From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM>

  98. Re: Transpose data using SQL (136 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  99. Re: Transpose data using SQL (108 lines)
    From: Ben <benpub7@YAHOO.COM>

  100. Re: Transpose data using SQL (98 lines)
    From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

  101. Transpose data using SQL (39 lines)
    From: Ben <benpub7@YAHOO.COM>

  102. Re: New Leadership Council for the SAS Community (77 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  103. Re: New Leadership Council for the SAS Community (66 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  104. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines)
    From: Rick Wicklin <Rick.Wicklin@SAS.COM>

  105. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines)
    From: .. <ajayohri@YAHOO.COM>

  106. Re: In() Function (168 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  107. Re: New Leadership Council for the SAS Community (44 lines)
    From: Teed, Lionel <Lionel.Teed@TD.COM>

  108. Re: Another weird discovery from coding error (38 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  109. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines)
    From: Rick Wicklin <rick.wicklin@SAS.COM>

  110. Re: Proc Tabulate question (12 lines)
    From: Wendi Wright <wendi_wright@CTB.COM>

  111. Re: Another weird discovery from coding error (24 lines)
    From: Rick Wicklin <rick.wicklin@SAS.COM>

  112. Re: Proc Tabulate question (57 lines)
    From: Wright, Wendi <Wendi_Wright@CTB.COM>

  113. Re: Datastep memory leak? (345 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  114. Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines)
    From: .. <ajayohri@YAHOO.COM>

  115. Re: New Leadership Council for the SAS Community (149 lines)
    From: Alan Churchill <savian.net@GMAIL.COM>

  116. Re: A couple of SAS efficiency questions (116 lines)
    From: Johnson Yuan <johnson.yuan@HOTMAIL.CO.NZ>

  117. Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429) (15 lines)
    From: Garabet, Angela <ANGELA.GARABET@LIBERTYMUTUAL.COM>

  118. Re: In() Function (166 lines)
    From: William W. Viergever <william@VIERGEVER.NET>

  119. Re: In() Function (135 lines)
    From: Paul Dorfman <sashole@BELLSOUTH.NET>

  120. Re: A couple of SAS efficiency questions (75 lines)
    From: Paul Dorfman <sashole@BELLSOUTH.NET>

  121. Re: Another weird discovery from coding error (45 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  122. Another weird discovery from coding error (25 lines)
    From: DUELL, BOB <bd9439@ATT.COM>

  123. Re: Proc Tabulate question (36 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  124. Re: Weighting Scheme in GLIMMIX? (105 lines)
    From: Steve Denham <stevedrd@YAHOO.COM>

  125. In() Function (11 lines)
    From: Titaan Titaan <titaan08@GMAIL.COM>

  126. Animated GIF using GREPLAY? (35 lines)
    From: Sadler, John <John.Sadler@ARS.USDA.GOV>

  127. Re: In() Function (65 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  128. Re: In() Function (60 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  129. Re: Proc Tabulate question (63 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  130. Re: New Leadership Council for the SAS Community (104 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  131. Re: Weighting Scheme in GLIMMIX? (143 lines)
    From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV>

  132. Proc Tabulate question (23 lines)
    From: Wendi Wright <wendi_wright@CTB.COM>

  133. Re: autoexec insert or append in 9.3 new option (54 lines)
    From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV>

  134. Re: New Leadership Council for the SAS Community (155 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  135. Re: A couple of SAS efficiency questions (77 lines)
    From: Zdeb, Michael S <mzdeb@ALBANY.EDU>

  136. Re: New Leadership Council for the SAS Community (214 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  137. Re: In() Function (228 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  138. Re: In() Function (193 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  139. Re: In() Function (175 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  140. Re: ACCESS/Oracle Lots of Messages (73 lines)
    From: DUELL, BOB <bd9439@ATT.COM>

  141. Re: SQL question (49 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  142. Re: In() Function (161 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  143. Re: In() Function (142 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  144. Re: SQL question (18 lines)
    From: Masoud Pajoh <mpajoh@ODOT.ORG>

  145. SQL question (13 lines)
    From: Masoud Pajoh <mpajoh@ODOT.ORG>

  146. Re: In() Function (127 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  147. Re: Weighting Scheme in GLIMMIX? (127 lines)
    From: R B <ryan.andrew.black@GMAIL.COM>

  148. Re: New Leadership Council for the SAS Community (74 lines)
    From: Rick Wicklin <Rick.Wicklin@SAS.COM>

  149. Re: Weighting Scheme in GLIMMIX? (45 lines)
    From: Steve Denham <stevedrd@YAHOO.COM>

  150. Re: autoexec insert or append in 9.3 new option (37 lines)
    From: Andre Wielki <wielki@INED.FR>

  151. autoexec insert or append in 9.3 new option (28 lines)
    From: Andre Wielki <wielki@INED.FR>

  152. Re: Proc format question (102 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  153. Re: In() Function (109 lines)
    From: Richard Read Allen <peakstat@WISPERTEL.NET>

  154. A couple of SAS efficiency questions (46 lines)
    From: Johnson Yuan <johnson.yuan@HOTMAIL.CO.NZ>

  155. Re: New Leadership Council for the SAS Community (91 lines)
    From: .. <ajayohri@YAHOO.COM>

  156. Weighting Scheme in GLIMMIX? (37 lines)
    From: R B <ryan.andrew.black@GMAIL.COM>

  157. ACCESS/Oracle Lots of Messages (59 lines)
    From: Alan Churchill <savian.net@GMAIL.COM>

  158. Re: In() Function (86 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  159. Re: In() Function (65 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  160. Re: In() Function (56 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  161. Re: In() Function (51 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  162. Re: In() Function (47 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  163. Re: In() Function (35 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  164. In() Function (7 lines)
    From: Titaan Titaan <titaan08@GMAIL.COM>

  165. Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (68 lines)
    From: Randy Herbison <RandyHerbison@WESTAT.COM>

  166. Importing Excel with Text content - Import.IO error (15 lines)
    From: Rob Hudson <caveatrob@GMAIL.COM>

  167. Re: New Leadership Council for the SAS Community (84 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  168. Re: font in data _NULL_ (53 lines)
    From: Randy Herbison <RandyHerbison@WESTAT.COM>

  169. Automatic reply: Proc format question (14 lines)
    From: Joe Morrissey <Joe.Morrissey@SAS.COM>

  170. Re: Proc format question (88 lines)
    From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV>

  171. Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (52 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  172. font in data _NULL_ (30 lines)
    From: sm dong <sasdong18@GMAIL.COM>

  173. Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (38 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  174. Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (44 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  175. Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (30 lines)
    From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM>

  176. Re: how to solve this senario? (22 lines)
    From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM>

  177. Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (22 lines)
    From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM>

  178. Re: how to solve this senario? (98 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  179. New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines)
    From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM>

  180. Re: Proc format question (64 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  181. Automatic reply: how to solve this senario? (14 lines)
    From: Muenchen, Robert A (Bob) <muenchen@UTK.EDU>

  182. how to solve this senario? (51 lines)
    From: Nway <hymadsk@GMAIL.COM>

  183. Re: In() Function (141 lines)
    From: William W. Viergever <william@VIERGEVER.NET>

  184. Re: In() Function (120 lines)
    From: Zdeb, Michael S <mzdeb@ALBANY.EDU>

  185. Re: simple datalines question (64 lines)
    From: Zdeb, Michael S <mzdeb@ALBANY.EDU>

  186. Re: Proc format question (152 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  187. Re: drawing a line representing a median on a bar chart (61 lines)
    From: DUELL, BOB <bd9439@ATT.COM>

  188. Re: Proc format question (141 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  189. Re: drawing a line representing a median on a bar chart (26 lines)
    From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM>

  190. Re: Proc format question (134 lines)
    From: Yu Zhang <zhangyu05@GMAIL.COM>

  191. Re: how to hash-object this? (116 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  192. Re: how to hash-object this? (151 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  193. Re: Proc format question (111 lines)
    From: DUELL, BOB <bd9439@ATT.COM>

  194. Re: Proc format question (52 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  195. drawing a line representing a median on a bar chart (29 lines)
    From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU>

  196. Re: how to hash-object this? (139 lines)
    From: oloolo <dynamicpanel@YAHOO.COM>

  197. Re: Proc format question (73 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  198. Re: how to hash-object this? (136 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  199. Re: Proc format question (59 lines)
    From: Yu Zhang <zhangyu05@GMAIL.COM>

  200. Re: Proc format question (49 lines)
    From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV>

  201. Re: how to hash-object this? (116 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  202. Proc format question (28 lines)
    From: Yu Zhang <zhangyu05@GMAIL.COM>

  203. Re: simple datalines question (83 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  204. Re: simple datalines question (52 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  205. simple datalines question (28 lines)
    From: adel F. <adel_tangi@YAHOO.FR>

  206. Re: Connections (29 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  207. Connections (23 lines)
    From: Ron Wells <Ron.Wells@SLFS.COM>

  208. Re: In() Function (87 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  209. Re: In() Function (75 lines)
    From: Zdeb, Michael S <mzdeb@ALBANY.EDU>

  210. Re: Howto Fix a dead SAS Log (54 lines)
    From: Ben Powell <bpowell555@GMAIL.COM>

  211. In() Function (44 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  212. Re: do not compute percent in proc freq out= data set (146 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  213. Re: do not compute percent in proc freq out= data set (129 lines)
    From: Mark Miller <mdhmiller@GMAIL.COM>

  214. Re: do not compute percent in proc freq out= data set (118 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  215. Re: do not compute percent in proc freq out= data set (108 lines)
    From: Fried Egg <friedegg2012@GMAIL.COM>

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