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: do not compute percent in proc freq out= data set (108 lines)
  2. Re: do not compute percent in proc freq out= data set (118 lines)
  3. Re: do not compute percent in proc freq out= data set (129 lines)
  4. Re: do not compute percent in proc freq out= data set (146 lines)
  5. In() Function (44 lines)
  6. Re: Howto Fix a dead SAS Log (54 lines)
  7. Re: In() Function (75 lines)
  8. Re: In() Function (87 lines)
  9. Connections (23 lines)
  10. Re: Connections (29 lines)
  11. simple datalines question (28 lines)
  12. Re: simple datalines question (52 lines)
  13. Re: simple datalines question (83 lines)
  14. Proc format question (28 lines)
  15. Re: how to hash-object this? (116 lines)
  16. Re: Proc format question (49 lines)
  17. Re: Proc format question (59 lines)
  18. Re: how to hash-object this? (136 lines)
  19. Re: Proc format question (73 lines)
  20. Re: how to hash-object this? (139 lines)
  21. drawing a line representing a median on a bar chart (29 lines)
  22. Re: Proc format question (52 lines)
  23. Re: Proc format question (111 lines)
  24. Re: how to hash-object this? (151 lines)
  25. Re: how to hash-object this? (116 lines)
  26. Re: Proc format question (134 lines)
  27. Re: drawing a line representing a median on a bar chart (26 lines)
  28. Re: Proc format question (141 lines)
  29. Re: drawing a line representing a median on a bar chart (61 lines)
  30. Re: Proc format question (152 lines)
  31. Re: simple datalines question (64 lines)
  32. Re: In() Function (120 lines)
  33. Re: In() Function (141 lines)
  34. how to solve this senario? (51 lines)
  35. Automatic reply: how to solve this senario? (14 lines)
  36. Re: Proc format question (64 lines)
  37. New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines)
  38. Re: how to solve this senario? (98 lines)
  39. Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (22 lines)
  40. Re: how to solve this senario? (22 lines)
  41. Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (30 lines)
  42. Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (44 lines)
  43. Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (38 lines)
  44. font in data _NULL_ (30 lines)
  45. Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (52 lines)
  46. Re: Proc format question (88 lines)
  47. Automatic reply: Proc format question (14 lines)
  48. Re: font in data _NULL_ (53 lines)
  49. Re: New Leadership Council for the SAS Community (84 lines)
  50. Importing Excel with Text content - Import.IO error (15 lines)
  51. Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (68 lines)
  52. In() Function (7 lines)
  53. Re: In() Function (35 lines)
  54. Re: In() Function (47 lines)
  55. Re: In() Function (51 lines)
  56. Re: In() Function (56 lines)
  57. Re: In() Function (65 lines)
  58. Re: In() Function (86 lines)
  59. ACCESS/Oracle Lots of Messages (59 lines)
  60. Weighting Scheme in GLIMMIX? (37 lines)
  61. Re: New Leadership Council for the SAS Community (91 lines)
  62. A couple of SAS efficiency questions (46 lines)
  63. Re: In() Function (109 lines)
  64. Re: Proc format question (102 lines)
  65. autoexec insert or append in 9.3 new option (28 lines)
  66. Re: autoexec insert or append in 9.3 new option (37 lines)
  67. Re: Weighting Scheme in GLIMMIX? (45 lines)
  68. Re: New Leadership Council for the SAS Community (74 lines)
  69. Re: Weighting Scheme in GLIMMIX? (127 lines)
  70. Re: In() Function (127 lines)
  71. SQL question (13 lines)
  72. Re: SQL question (18 lines)
  73. Re: In() Function (142 lines)
  74. Re: In() Function (161 lines)
  75. Re: SQL question (49 lines)
  76. Re: ACCESS/Oracle Lots of Messages (73 lines)
  77. Re: In() Function (175 lines)
  78. Re: In() Function (193 lines)
  79. Re: In() Function (228 lines)
  80. Re: New Leadership Council for the SAS Community (214 lines)
  81. Re: A couple of SAS efficiency questions (77 lines)
  82. Re: New Leadership Council for the SAS Community (155 lines)
  83. Re: autoexec insert or append in 9.3 new option (54 lines)
  84. Proc Tabulate question (23 lines)
  85. Re: Weighting Scheme in GLIMMIX? (143 lines)
  86. Re: New Leadership Council for the SAS Community (104 lines)
  87. Re: Proc Tabulate question (63 lines)
  88. Re: In() Function (60 lines)
  89. Re: In() Function (65 lines)
  90. Animated GIF using GREPLAY? (35 lines)
  91. In() Function (11 lines)
  92. Re: Weighting Scheme in GLIMMIX? (105 lines)
  93. Re: Proc Tabulate question (36 lines)
  94. Another weird discovery from coding error (25 lines)
  95. Re: Another weird discovery from coding error (45 lines)
  96. Re: A couple of SAS efficiency questions (75 lines)
  97. Re: In() Function (135 lines)
  98. Re: In() Function (166 lines)
  99. Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429) (15 lines)
  100. Re: A couple of SAS efficiency questions (116 lines)
  101. Re: New Leadership Council for the SAS Community (149 lines)
  102. Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines)
  103. Re: Datastep memory leak? (345 lines)
  104. Re: Proc Tabulate question (57 lines)
  105. Re: Another weird discovery from coding error (24 lines)
  106. Re: Proc Tabulate question (12 lines)
  107. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines)
  108. Re: Another weird discovery from coding error (38 lines)
  109. Re: New Leadership Council for the SAS Community (44 lines)
  110. Re: In() Function (168 lines)
  111. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines)
  112. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines)
  113. Re: New Leadership Council for the SAS Community (66 lines)
  114. Re: New Leadership Council for the SAS Community (77 lines)
  115. Transpose data using SQL (39 lines)
  116. Re: Transpose data using SQL (98 lines)
  117. Re: Transpose data using SQL (108 lines)
  118. Re: Transpose data using SQL (136 lines)
  119. Re: Transpose data using SQL (24 lines)
  120. Re: New Leadership Council for the SAS Community (89 lines)
  121. Re: Transpose data using SQL (154 lines)
  122. Re: Transpose data using SQL (167 lines)
  123. Re: Transpose data using SQL (9 lines)
  124. Re: Transpose data using SQL (28 lines)
  125. Re: Transpose data using SQL (175 lines)
  126. Re: Transpose data using SQL (14 lines)
  127. Re: Transpose data using SQL (24 lines)
  128. Re: Transpose data using SQL (104 lines)
  129. Programmtically accessing WRS Reports (21 lines)
  130. SQL: joining on closest datetime match (37 lines)
  131. Re: Transpose data using SQL (32 lines)
  132. Re: Datastep memory leak? (390 lines)
  133. Re: SQL: joining on closest datetime match (44 lines)
  134. Re: Transpose data using SQL (28 lines)
  135. Re: SQL: joining on closest datetime match (79 lines)
  136. Re: Datastep memory leak? (431 lines)
  137. Re: Transpose data using SQL (39 lines)
  138. Re: Transpose data using SQL (51 lines)
  139. Re: A couple of SAS efficiency questions (133 lines)
  140. Re: In() Function (214 lines)
  141. Re: joining on closest datetime match (84 lines)
  142. Re: SQL: joining on closest datetime match (63 lines)
  143. Re: SQL: joining on closest datetime match (93 lines)
  144. Re: In() Function (268 lines)
  145. Re: Programmtically accessing WRS Reports (38 lines)
  146. Re: Transpose data using SQL (66 lines)
  147. Re: Programmtically accessing WRS Reports (50 lines)
  148. Re: SQL: joining on closest datetime match (60 lines)
  149. Re: New Leadership Council for the SAS Community (89 lines)
  150. Re: SQL: joining on closest datetime match (97 lines)
  151. Re: Transpose data using SQL (21 lines)
  152. Re: joining on closest datetime match (73 lines)
  153. An Interesting (I think) PROC MIanalyze Question (90 lines)
  154. Re: Transpose data using SQL (83 lines)
  155. Re: Programmtically accessing WRS Reports (65 lines)
  156. Re: Creating Folder Dynamically in SAS (64 lines)
  157. PROC MIanalyze and Descriptive Statistics Question (91 lines)
  158. Re: Creating Folder Dynamically in SAS (79 lines)
  159. Re: Datastep memory leak? (422 lines)
  160. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines)
  161. Re: Transpose data using SQL (28 lines)
  162. Re: Datastep memory leak? (127 lines)
  163. Re: Datastep memory leak? (224 lines)
  164. Re: Programmtically accessing WRS Reports (55 lines)
  165. Re: Datastep memory leak? (286 lines)
  166. Re: Transpose data using SQL (39 lines)
  167. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines)
  168. New trojan going around (12 lines)
  169. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines)
  170. Conidence interval (xbar-2*ybar) (17 lines)
  171. Re: SQL: joining on closest datetime match (133 lines)
  172. Re: Q: need to nest PDF bookmarks (112 lines)
  173. Re: Conidence interval (xbar-2*ybar) (38 lines)
  174. Re: Conidence interval (xbar-2*ybar) (10 lines)
  175. Re: Creating Folder Dynamically in SAS (102 lines)
  176. Re: In() Function (266 lines)
  177. Re: In() Function (86 lines)
  178. Re: Confidence interval (xbar-2*ybar) (28 lines)
  179. Code (13 lines)
  180. Re: Code (46 lines)
  181. Re: Code (33 lines)
  182. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines)
  183. Re: Code (62 lines)
  184. Re: Code (69 lines)
  185. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines)
  186. Graphing GLM Regression Equation Against Dummy Values (23 lines)
  187. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines)
  188. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines)
  189. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines)
  190. Re: Graphing GLM Regression Equation Against Dummy Values (41 lines)
  191. Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines)
  192. Re: Code (25 lines)
  193. Re: SQL: joining on closest datetime match (164 lines)
  194. Re: SQL: joining on closest datetime match (179 lines)
  195. Re: SQL: joining on closest datetime match (215 lines)
  196. Re: Graphing GLM Regression Equation Against Dummy Values (29 lines)
  197. Re: Graphing GLM Regression Equation Against Dummy Values (44 lines)
  198. Re: SQL: joining on closest datetime match (507 lines)
  199. Re: SQL: joining on closest datetime match (249 lines)
  200. Re: SQL: joining on closest datetime match (258 lines)
  201. Re: Graphing GLM Regression Equation Against Dummy Values (28 lines)
  202. Longitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines)
  203. Re: Graphing GLM Regression Equation Against Dummy Values (104 lines)
  204. Dates when extracting data from SQL server with PROC SQL (59 lines)
  205. Re: Dates when extracting data from SQL server with PROC SQL (96 lines)
  206. Re: New Leadership Council for the SAS Community (76 lines)
  207. Re: SQL: joining on closest datetime match (178 lines)
  208. Re: Graphing GLM Regression Equation Against Dummy Values (121 lines)
  209. Re: SQL: joining on closest datetime match (447 lines)
  210. Re: SQL: joining on closest datetime match (636 lines)
  211. Re: SQL: joining on closest datetime match (64 lines)
  212. Re: SQL: joining on closest datetime match (633 lines)
  213. Re: SQL: joining on closest datetime match (712 lines)
  214. Re: SQL: joining on closest datetime match (751 lines)
  215. Re: Creating Folder Dynamically in SAS (23 lines)
Back to the main SAS-L page
listserv.uga.edu
Enterprise Information Technology Services
The University of Georgia
listhelp@uga.edu