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 2011, week 4

  1. Re: A Data manupulation question (21 lines)
  2. Re: A Data manupulation question (38 lines)
  3. Changing a grid of month by year data to a column (50 lines)
  4. Re: SQL pass through Oracle date? (169 lines)
  5. Re: SQL pass through Oracle date? (83 lines)
  6. Re: Somewhat OT: Length=0 Oracle column cause trouble (58 lines)
  7. Re: compare multi variables' values (67 lines)
  8. Re: Changing a grid of month by year data to a column (28 lines)
  9. Open Source Reader of SAS Data Sets (32 lines)
  10. macro quoting functions, comilation vs exectution (18 lines)
  11. Re: compare multi variables' values (20 lines)
  12. Re: importing messy dates (15 lines)
  13. Re: compare multi variables' values (26 lines)
  14. Re: compare multi variables' values (51 lines)
  15. Job Opportunity / TS Clearance required / Northern VA (35 lines)
  16. Re: SQL pass through Oracle date? (98 lines)
  17. Open code statement recursion detected, macro code (38 lines)
  18. Minus sign hex code? (15 lines)
  19. Re: A Data manupulation question (37 lines)
  20. Re: SQL pass through Oracle date? (116 lines)
  21. Re: Open code statement recursion detected, macro code (50 lines)
  22. Re: SQL pass through Oracle date? (97 lines)
  23. Re: compare multi variables' values (133 lines)
  24. Re: Open code statement recursion detected, macro code (72 lines)
  25. Re: Installation of SAS-callable SUDAAN (58 lines)
  26. Re: finding maximum of multiple variables over multiple date windows (502 lines)
  27. Re: compare multi variables' values (80 lines)
  28. Re: compare multi variables' values (175 lines)
  29. Re: compare multi variables' values (106 lines)
  30. Re: compare multi variables' values (95 lines)
  31. Re: Minus sign hex code? (18 lines)
  32. SAS Log Issue (20 lines)
  33. Re: Minus sign hex code? (51 lines)
  34. Re: compare multi variables' values (179 lines)
  35. Re: compare multi variables' values (114 lines)
  36. Re: Installation of SAS-callable SUDAAN (63 lines)
  37. A MAX Function question (28 lines)
  38. Re: A MAX Function question (48 lines)
  39. Re: A MAX Function question (58 lines)
  40. Re: A MAX Function question (68 lines)
  41. Re: finding maximum of multiple variables over multiple date windows (576 lines)
  42. SAS Log Issue (42 lines)
  43. Re: SAS Log Issue (11 lines)
  44. Re: creating new variables from variable names stored in another variable (102 lines)
  45. Re: A MAX Function question (112 lines)
  46. Re: SAS Log Issue (54 lines)
  47. Re: Installation of SAS-callable SUDAAN (88 lines)
  48. pulling text out of a specific string of data (37 lines)
  49. Re: SAS Log Issue (54 lines)
  50. Re: A MAX Function question (128 lines)
  51. Re: Open code statement recursion detected, macro code (80 lines)
  52. pulling text out of a specific string of data (39 lines)
  53. Raw and Standardized Betas from Proc Surveyreg (42 lines)
  54. proc report (25 lines)
  55. Re: pulling text out of a specific string of data (80 lines)
  56. Proc report (29 lines)
  57. Re: Raw and Standardized Betas from Proc Surveyreg (38 lines)
  58. Uploading SAS to teradata (17 lines)
  59. Re: compare multi variables' values (101 lines)
  60. Re: Proc report (51 lines)
  61. Automatic reply: Proc report (11 lines)
  62. Re: Uploading SAS to teradata (86 lines)
  63. Re: compare multi variables' values (114 lines)
  64. dates really messed up in Excel, how to import to SAS? (31 lines)
  65. Re: pulling text out of a specific string of data (126 lines)
  66. Re: dates really messed up in Excel, how to import to SAS? (55 lines)
  67. Re: dates really messed up in Excel, how to import to SAS? (54 lines)
  68. Re: pulling text out of a specific string of data (145 lines)
  69. Re: dates really messed up in Excel, how to import to SAS? (99 lines)
  70. Re: dates really messed up in Excel, how to import to SAS? (217 lines)
  71. Re: dates really messed up in Excel, how to import to SAS? (112 lines)
  72. Re: dates really messed up in Excel, how to import to SAS? (123 lines)
  73. Re: dates really messed up in Excel, how to import to SAS? (110 lines)
  74. NLMIXED for a DID model (41 lines)
  75. Need help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines)
  76. Re: compare multi variables' values (172 lines)
  77. Building Z-Score calculation for Pediatric Blood Pressures (30 lines)
  78. Re: pulling text out of a specific string of data (209 lines)
  79. Re: finding maximum of multiple variables over multiple date windows (566 lines)
  80. How to read .dmp files (20 lines)
  81. Re: How to read .dmp files (31 lines)
  82. Re: pulling text out of a specific string of data (223 lines)
  83. Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines)
  84. Re: pulling text out of a specific string of data (91 lines)
  85. Re: How to read .dmp files (78 lines)
  86. Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines)
  87. Re: How to read .dmp files (91 lines)
  88. Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines)
  89. Re: Open code statement recursion detected, macro code (110 lines)
  90. Re: Open code statement recursion detected, macro code (159 lines)
  91. Re: dates really messed up in Excel, how to import to SAS? (125 lines)
  92. Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines)
  93. Re: pulling text out of a specific string of data (161 lines)
  94. Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines)
  95. <No subject> (10 lines)
  96. Re: pulling text out of a specific string of data (207 lines)
  97. Re: problems with locks on stored macros (135 lines)
  98. Re: dates really messed up in Excel, how to import to SAS? (182 lines)
  99. Estimate Statement PROC NLMIXED (30 lines)
  100. Re: Estimate Statement PROC NLMIXED (76 lines)
  101. Re: Estimate Statement PROC NLMIXED (137 lines)
  102. Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628) (16 lines)
  103. Re: dates really messed up in Excel, how to import to SAS? (13 lines)
  104. Re: titles >256 and dictionary.titles (103 lines)
  105. data manipulation help (30 lines)
  106. Re: data manipulation help (89 lines)
  107. Re: dates really messed up in Excel, how to import to SAS? (24 lines)
  108. Re: SAS 9.3? (15 lines)
  109. Re: data manipulation help (34 lines)
  110. Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines)
  111. Re: data manipulation help (41 lines)
  112. Re: titles >256 and dictionary.titles (113 lines)
  113. Re: SAS 9.3? (46 lines)
  114. Re: data manipulation help (39 lines)
  115. Job announcement on linkedin (13 lines)
  116. Re: dates really messed up in Excel, how to import to SAS? (41 lines)
  117. STAT problem (22 lines)
  118. Re: titles >256 and dictionary.titles (120 lines)
  119. Re: titles >256 and dictionary.titles (127 lines)
  120. sas discussion forums are moving! (26 lines)
  121. Re: STAT problem (34 lines)
  122. Re: STAT problem (37 lines)
  123. Re: STAT problem (44 lines)
  124. Re: Building Z-Score calculation for Pediatric Blood Pressures (17 lines)
  125. Re: SAS 9.3? (37 lines)
  126. Re: STAT problem (64 lines)
  127. Re: STAT problem (57 lines)
  128. Re: STAT problem (66 lines)
  129. Re: STAT problem (78 lines)
  130. Re: STAT problem (33 lines)
  131. Re: STAT problem (57 lines)
  132. Re: STAT problem (186 lines)
  133. Re: STAT problem (97 lines)
  134. %sysfunc( ), trailing and leading blanks (27 lines)
  135. Re: %sysfunc( ), trailing and leading blanks (59 lines)
  136. Re: %sysfunc( ), trailing and leading blanks (43 lines)
  137. Merge (30 lines)
  138. Re: dates really messed up in Excel, how to import to SAS? (37 lines)
  139. Re: Merge (16 lines)
  140. Re: data manipulation help (11 lines)
  141. Re: ExcelXP ODS Tagset Question (25 lines)
  142. Re: %sysfunc( ), trailing and leading blanks (71 lines)
  143. Re: dates really messed up in Excel, how to import to SAS? (43 lines)
  144. Installing SAS (22 lines)
  145. Re: Merge (44 lines)
  146. SCL program (25 lines)
  147. Re: SCL program (44 lines)
  148. Re: SCL program (59 lines)
  149. Re: SCL program (65 lines)
  150. Re: SCL program (81 lines)
  151. Re: SCL program (100 lines)
  152. code repeated in log wihout further actions (35 lines)
  153. Re: code repeated in log wihout further actions (48 lines)
  154. weird log notes (71 lines)
  155. Re: weird log notes (81 lines)
  156. Re: weird log notes (78 lines)
  157. Re: weird log notes (97 lines)
  158. parMbuff (18 lines)
  159. Re: parMbuff (31 lines)
  160. what's wrong with adding %str(,), parmbuff (37 lines)
  161. Re: parMbuff (46 lines)
  162. Re: what's wrong with adding %str(,), parmbuff (58 lines)
  163. Re: parMbuff (55 lines)
  164. Re: what's wrong with adding %str(,), parmbuff (102 lines)
  165. Re: what's wrong with adding %str(,), parmbuff (107 lines)
  166. macro variable inside and outside a macro (93 lines)
  167. Re: what's wrong with adding %str(,), parmbuff (127 lines)
  168. Re: macro variable inside and outside a macro (105 lines)
  169. the benefit of using parmbuff option with MACROS (53 lines)
  170. Re: the benefit of using parmbuff option with MACROS (80 lines)
  171. Re: Changing a grid of month by year data to a column (76 lines)
  172. Reg: Portal Issue (15 lines)
  173. PUT function (61 lines)
  174. Re: PUT function (83 lines)
  175. Re: PUT function (78 lines)
  176. Re: PUT function (141 lines)
  177. PC SAS - Reading jpeg images. (54 lines)
  178. Re: PUT function (99 lines)
  179. ODS output to excel sheets (81 lines)
  180. Re: ODS output to excel sheets (94 lines)
  181. Re: ODS output to excel sheets (76 lines)
  182. Re: ODS output to excel sheets (103 lines)
  183. Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636) (22 lines)
  184. Re: ODS output to excel sheets (130 lines)
  185. Re: ODS output to excel sheets (137 lines)
  186. Re: ODS output to excel sheets (135 lines)
  187. Re: ODS output to excel sheets (159 lines)
  188. Tracking SQL progress (78 lines)
  189. Re: Tracking SQL progress (101 lines)
  190. Re: Installation of SAS-callable SUDAAN (96 lines)
  191. Re: the benefit of using parmbuff option with MACROS (100 lines)
  192. New Yok SUG (31 lines)
  193. Count data overdispersion – not due to zero inflation (51 lines)
  194. Re: the benefit of using parmbuff option with MACROS (71 lines)
  195. Re: the benefit of using parmbuff option with MACROS (111 lines)
  196. Re: New Yok SUG (50 lines)
  197. Re: Tracking SQL progress (89 lines)
  198. Re: PC SAS - Reading jpeg images. (87 lines)
  199. How to use SAS Macro to make data comparisons much more efficient? (44 lines)
  200. Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines)
  201. Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines)
  202. Re: PC SAS - Reading jpeg images. (93 lines)
  203. Re: PC SAS - Reading jpeg images. (103 lines)
  204. regex question (35 lines)
  205. =?windows-1252?Q?Re=3A_Count_data_overdispersion_=E2=80=93_not_due_to_ze?= =?windows-1252?Q?ro_inflation?= (77 lines)
  206. Re: regex question (94 lines)
  207. Re: regex question (57 lines)
  208. Analytics 2011 - SAS Data Mining Conference (15 lines)
  209. getting the last four numbers as name of data set (28 lines)
  210. Re: getting the last four numbers as name of data set (55 lines)
  211. Re: Merge (81 lines)
  212. Re: Tracking SQL progress (112 lines)
  213. Re: PC SAS - Reading jpeg images. (120 lines)
  214. Re: regex question (18 lines)
  215. Job Opportunities in the Washington, DC Area (147 lines)
  216. column width question in Proc Report (40 lines)
  217. OT: Friday Humor (19 lines)
  218. Re: getting the last four numbers as name of data set (62 lines)
  219. Re: OT: Friday Humor (27 lines)
  220. Re: OT: Friday Humor (49 lines)
  221. Re: column width question in Proc Report (72 lines)
  222. Hot fix warning - SAS 9.2M3 Solaris (34 lines)
  223. Using Numbers in Macro Do-Loops for Dates (37 lines)
  224. Re: Long text fields in Excel (178 lines)
  225. Re: Using Numbers in Macro Do-Loops for Dates (80 lines)
  226. Re: OT: Friday Humor (59 lines)
  227. Re: Using Numbers in Macro Do-Loops for Dates (42 lines)
  228. Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines)
  229. Re: Using Numbers in Macro Do-Loops for Dates (78 lines)
  230. Re: Using Numbers in Macro Do-Loops for Dates (80 lines)
  231. Re: Using Numbers in Macro Do-Loops for Dates (84 lines)
  232. Re: Using Numbers in Macro Do-Loops for Dates (67 lines)
  233. Re: Using Numbers in Macro Do-Loops for Dates (96 lines)
  234. What is "IN" called when used in a merge statement? (31 lines)
  235. Re: What is "IN" called when used in a merge statement? (41 lines)
  236. Re: Using Numbers in Macro Do-Loops for Dates (32 lines)
  237. Re: Using Numbers in Macro Do-Loops for Dates (41 lines)
  238. Automatic reply: Using Numbers in Macro Do-Loops for Dates (19 lines)
  239. Re: What is "IN" called when used in a merge statement? (51 lines)
Back to the main SAS-L page