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 – March 2011, week 1

  1. Re: Saturday Night Humor (was MAX() function over character values) (192 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  2. Re: Segmentation violation error in hash table lookup (144 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  3. Re: importint lots of txt files at once and taking the date from the title (22 lines)
    From: Nuria Chapinal <nchapinal@YAHOO.COM>

  4. Re: Working with time data in SAS XXXX (91 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  5. Reminder: Toronto Area SAS Society (TASS) March Meeting (84 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  6. Re: Apply to be Conference Chair - SAS Global Forum 2104 (33 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  7. Re: What Goptions need to be used ?? (111 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  8. Re: Apply to be Conference Chair - SAS Global Forum 2104 (71 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  9. Re: What Goptions need to be used ?? (137 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  10. where I can find SAS macro for weighted GEE? (17 lines)
    From: hua gang <hg448@YAHOO.COM>

  11. PROC GPLOT and Annotate: Examples of shaded vertical regions (28 lines)
    From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>

  12. Re: What Goptions need to be used ?? (158 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  13. Re: PROC GPLOT and Annotate: Examples of shaded vertical regions (90 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  14. Re: where I can find SAS macro for weighted GEE? (43 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  15. Bar Chart (46 lines)
    From: David Friedman <harrypotterdhf@EARTHLINK.NET>

  16. Re: where I can find SAS macro for weighted GEE? (28 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  17. Solution to "importing lots of txt files at once and taking the date from the title" (28 lines)
    From: Nuria Chapinal <nchapinal@YAHOO.COM>

  18. Re: Bar Chart (61 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  19. Re: horizontal to vertical data structure - take 2 (200 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  20. Re: Saturday Night Humor (was MAX() function over character values) (230 lines)
    From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

  21. NJ SAS Users Group Meeting: March 25th at Rutgers University (32 lines)
    From: Ted Vittas <nj.sas.users.group@GMAIL.COM>

  22. Re: PROC GPLOT and Annotate: Examples of shaded vertical regions (231 lines)
    From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>

  23. Re: Working with time data in SAS XXXX (77 lines)
    From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>

  24. Re: Apply to be Conference Chair - SAS Global Forum 2104 (90 lines)
    From: Kirby, Ted <ted.kirby@LEWIN.COM>

  25. Re: Apply to be Conference Chair - SAS Global Forum 2104 (118 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  26. Re: Apply to be Conference Chair - SAS Global Forum 2104 (120 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  27. Re: PROC GPLOT and Annotate: Examples of shaded vertical regions (248 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  28. proc contents (15 lines)
    From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>

  29. Re: proc contents (45 lines)
    From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>

  30. Fuzzy name matching (39 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  31. Re: Fuzzy name matching (50 lines)
    From: Mark Miller <mdhmiller@GMAIL.COM>

  32. Re: proc contents (70 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  33. Re: proc contents (46 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  34. Re: Fuzzy name matching (72 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  35. Re: Fuzzy name matching (48 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  36. Re: proc contents (81 lines)
    From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>

  37. Re: Fuzzy name matching (64 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  38. Re: proc contents (104 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  39. Re: Fuzzy name matching (78 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  40. Re: proc contents (95 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  41. Re: Fuzzy name matching (90 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  42. Re: Fuzzy name matching (107 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  43. Re: Fuzzy name matching (110 lines)
    From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

  44. Re: Fuzzy name matching (23 lines)
    From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV>

  45. Re: Saturday Night Humor (was MAX() function over character values) (220 lines)
    From: Paul Dorfman <sashole@BELLSOUTH.NET>

  46. Re: PROC GPLOT and Annotate: Examples of shaded vertical regions (263 lines)
    From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>

  47. Re: proc contents (51 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  48. Re: proc contents (108 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  49. Re: proc contents (81 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  50. Re: proc contents (148 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  51. Using "(OF" With Comma-Separated List (26 lines)
    From: Kristin Graves <gravesk@CONED.COM>

  52. Re: PROC GPLOT and Annotate: Examples of shaded vertical regions (285 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  53. Re: Using "(OF" With Comma-Separated List (35 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  54. Re: Using "(OF" With Comma-Separated List (47 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  55. Re: proc contents (204 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  56. Better ways to put value into Macro variable during data step? (43 lines)
    From: Bian, Haikuo <HBian@NW7.ESRD.NET>

  57. Re: proc contents (223 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  58. Re: proc contents (241 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  59. Re: Using "(OF" With Comma-Separated List (47 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  60. Since what SAS vs does ATTRIB exist? (17 lines)
    From: Jim Groeneveld <jim.1stat@YAHOO.COM>

  61. Re: Better ways to put value into Macro variable during data step? (92 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  62. Re: PROC GPLOT and Annotate: Examples of shaded vertical regions (271 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  63. Re: Better ways to put value into Macro variable during data step? (102 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  64. Text Box in GCHART or GPLOT (17 lines)
    From: David Friedman <harrypotterdhf@EARTHLINK.NET>

  65. Re: proc contents (273 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  66. ODS (9 lines)
    From: William Shakespeare <shakespeare_1040@HOTMAIL.COM>

  67. Re: proc contents (268 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  68. Re: Text Box in GCHART or GPLOT (25 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  69. Re: Better ways to put value into Macro variable during data step? (114 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  70. Re: ODS (34 lines)
    From: Kirby, Ted <ted.kirby@LEWIN.COM>

  71. Re: ODS (20 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  72. Re: Better ways to put value into Macro variable during data step? (118 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  73. Re: Text Box in GCHART or GPLOT (16 lines)
    From: David Friedman <harrypotterdhf@EARTHLINK.NET>

  74. Gap Determination (29 lines)
    From: Dave <david.brewer@UC.EDU>

  75. Using "call" function within PROC SQL ? (43 lines)
    From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV>

  76. Survey logistic warnings (53 lines)
    From: Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>

  77. Re: Since what SAS vs does ATTRIB exist? (36 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  78. Re: Gap Determination (67 lines)
    From: Blackburn, Taylor <Blackburn.Taylor@BLS.GOV>

  79. Re: Better ways to put value into Macro variable during data step? (64 lines)
    From: Chang Chung <chang_y_chung@HOTMAIL.COM>

  80. Re: Better ways to put value into Macro variable during data step_side question added (133 lines)
    From: Bian, Haikuo <HBian@NW7.ESRD.NET>

  81. Re: Survey logistic warnings (68 lines)
    From: Jonas Bilenas <jonas.bilenas@CHASE.COM>

  82. Re: Better ways to put value into Macro variable during data step_side question added (138 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  83. Re: Gap Determination (73 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  84. Re: Better ways to put value into Macro variable during data step_side question added (149 lines)
    From: Bian, Haikuo <HBian@NW7.ESRD.NET>

  85. Re: Gap Determination (76 lines)
    From: Dave Brewer <david.brewer@UC.EDU>

  86. Re: Gap Determination (95 lines)
    From: Blackburn, Taylor <Blackburn.Taylor@BLS.GOV>

  87. Re: Gap Determination (104 lines)
    From: Dave Brewer <DAvid.brewer@UC.EDU>

  88. Re: Gap Determination (134 lines)
    From: Blackburn, Taylor <Blackburn.Taylor@BLS.GOV>

  89. Re: Gap Determination (85 lines)
    From: Dave Brewer <DAvid.brewer@UC.EDU>

  90. Re: Gap Determination (159 lines)
    From: Dave Brewer <DAvid.brewer@UC.EDU>

  91. Re: Gap Determination (173 lines)
    From: Blackburn, Taylor <Blackburn.Taylor@BLS.GOV>

  92. Regarding SGF Hotel Reservations (17 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  93. Automatic reply: Gap Determination (19 lines)
    From: Jan Squillace <Jan.Squillace@SAS.COM>

  94. Re: Regarding SGF Hotel Reservations (32 lines)
    From: F J Kelley <jkelley@UGA.EDU>

  95. SAS -- PUT and File Commands (29 lines)
    From: Brian Trautman <btrautman84@GMAIL.COM>

  96. Re: ODS (17 lines)
    From: William Shakespeare <shakespeare_1040@HOTMAIL.COM>

  97. Re: SAS -- PUT and File Commands (41 lines)
    From: Mark Miller <mdhmiller@GMAIL.COM>

  98. Re: ODS (36 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  99. Re: SAS -- PUT and File Commands (61 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  100. Re: ODS (50 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  101. Re: ODS (34 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  102. PROC TABULATE BY statement label replacement (162 lines)
    From: White, Svend A. <SvendW@HEALTH.OK.GOV>

  103. Re: Gap Determination (184 lines)
    From: Dave Brewer <david.brewer@UC.EDU>

  104. File locking (42 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  105. Re: PROC TABULATE BY statement label replacement (186 lines)
    From: Thomas Rick <RThomas@WOOLWORTHS.COM.AU>

  106. Re: PROC TABULATE BY statement label replacement (196 lines)
    From: White, Svend A. <SvendW@HEALTH.OK.GOV>

  107. Re: PROC TABULATE BY statement label replacement (203 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  108. column names only (12 lines)
    From: Sharat Sharma <sharat.katz@GMAIL.COM>

  109. PROC DISTANCE (86 lines)
    From: Long, Stuart (NIH/NIEHS) [C] <long3@NIEHS.NIH.GOV>

  110. eval the expression in variable (14 lines)
    From: Clark An <kuhasu@126.COM>

  111. Re: eval the expression in variable (32 lines)
    From: vaibhav wadhera <vaibhavwadhera@GMAIL.COM>

  112. Re: PROC DISTANCE (92 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  113. Re: column names only (33 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  114. Re: column names only (49 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  115. Re: PROC DISTANCE (93 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  116. Re: Gap Determination (203 lines)
    From: Mike Rhoads <RHOADSM1@WESTAT.COM>

  117. Re: PROC DISTANCE (112 lines)
    From: Long, Stuart (NIH/NIEHS) [C] <long3@NIEHS.NIH.GOV>

  118. Re: PROC DISTANCE (117 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  119. Re: Gap Determination (190 lines)
    From: Dave Brewer <david.brewer@UC.EDU>

  120. MIME: multipart/alternative with different plain and html content (32 lines)
    From: Manuel David Garcia <manueldavid.garcia@VERIVOX.COM>

  121. Re: eval the expression in variable (46 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  122. Re: MIME: multipart/alternative with different plain and html content (50 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  123. a function or quick way to compute average with min number of non-missing data points (23 lines)
    From: hua gang <hg448@YAHOO.COM>

  124. Re: a function or quick way to compute average with min number of non-missing data points (61 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  125. Re: a function or quick way to compute average with min number of non-missing data points (52 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  126. Re: a function or quick way to compute average with min number of non-missing data points (30 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  127. Re: a function or quick way to compute average with min number of non-missing data points (35 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  128. Re: PROC TABULATE BY statement label replacement (223 lines)
    From: White, Svend A. <SvendW@HEALTH.OK.GOV>

  129. Re: eval the expression in variable (13 lines)
    From: Clark An <kuhasu@126.COM>

  130. Re: eval the expression in variable (21 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  131. Re: eval the expression in variable (34 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  132. replacing var name with label in multiway list format (49 lines)
    From: Yu Zhang <zhangyu05@GMAIL.COM>

  133. Re: eval the expression in variable (37 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  134. Re: eval the expression in variable (10 lines)
    From: Clark An <kuhasu@126.COM>

  135. Re: eval the expression in variable (37 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  136. Re: eval the expression in variable (30 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  137. Re: eval the expression in variable (47 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  138. Re: eval the expression in variable (62 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  139. Data manipulation (25 lines)
    From: Steve Steve <steve11145@YAHOO.COM>

  140. proc sql (48 lines)
    From: John Mike <sasslick@GMAIL.COM>

  141. Re: eval the expression in variable (9 lines)
    From: Clark An <kuhasu@126.COM>

  142. Re: eval the expression in variable (41 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  143. Re: eval the expression in variable (9 lines)
    From: Clark An <kuhasu@126.COM>

  144. Re: Data manipulation (78 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  145. ods and color in the printout as a highlight of differences in the table: (32 lines)
    From: Aldi Kraja <aldi@WUSTL.EDU>

  146. Re: eval the expression in variable (13 lines)
    From: Clark An <kuhasu@126.COM>

  147. Re: eval the expression in variable (7 lines)
    From: Clark An <kuhasu@126.COM>

  148. famous "SQL-L" ? (17 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  149. Re: eval the expression in variable (19 lines)
    From: Clark An <kuhasu@126.COM>

  150. Re: ods and color in the printout as a highlight of differences in the table: (78 lines)
    From: Aldi Kraja <aldi@WUSTL.EDU>

  151. Re: Data manipulation (36 lines)
    From: Steve Steve <steve11145@YAHOO.COM>

  152. Re: eval the expression in variable (42 lines)
    From: oloolo <dynamicpanel@YAHOO.COM>

  153. Re: proc sql (184 lines)
    From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

  154. Re: Data manipulation (81 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  155. Re: proc sql (191 lines)
    From: John Mike <sasslick@GMAIL.COM>

  156. Re: proc sql (237 lines)
    From: John Mike <sasslick@GMAIL.COM>

  157. Re: proc sql (241 lines)
    From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

  158. Re: proc sql (72 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  159. Re: famous "SQL-L" ? (30 lines)
    From: Mary <mlhoward@AVALON.NET>

  160. Proc Sort nodupkey for all columns (26 lines)
    From: Irin later <irinfigvam@YAHOO.COM>

  161. Re: Proc Sort nodupkey for all columns (32 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  162. Re: Proc Sort nodupkey for all columns (48 lines)
    From: Irin later <irinfigvam@YAHOO.COM>

  163. Re: ods and color in the printout as a highlight of differences in the table: (109 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  164. Re: Proc Sort nodupkey for all columns (52 lines)
    From: Mark Miller <mdhmiller@GMAIL.COM>

  165. Re: ods and color in the printout as a highlight of differences in the table: (63 lines)
    From: Randy Herbison <RandyHerbison@WESTAT.COM>

  166. Re: Proc Sort nodupkey for all columns (59 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  167. weighted kappa using GEE for test-retest (67 lines)
    From: Penfold, Robert <penfold.r@GHC.ORG>

  168. Re: eval the expression in variable (21 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  169. Re: Proc Sort nodupkey for all columns (112 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  170. Re: Proc Sort nodupkey for all columns (132 lines)
    From: Mark Miller <mdhmiller@GMAIL.COM>

  171. Re: Proc Sort nodupkey for all columns (138 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  172. Re: eval the expression in variable (9 lines)
    From: Clark An <kuhasu@126.COM>

  173. Re: MIME: multipart/alternative with different plain and html content (55 lines)
    From: Alan Churchill <alan.churchill@SAVIAN.NET>

  174. Re: Better ways to put value into Macro variable during data step_side question added (184 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  175. Re: column names only (47 lines)
    From: Sharat Sharma <sharat.katz@GMAIL.COM>

  176. Re: Gap Determination (67 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  177. Re: eval the expression in variable (27 lines)
    From: Clark An <kuhasu@126.COM>

  178. Re: eval the expression in variable (7 lines)
    From: Clark An <kuhasu@126.COM>

  179. Re: eval the expression in variable (9 lines)
    From: Clark An <kuhasu@126.COM>

  180. Re: Proc Sort nodupkey for all columns (163 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  181. Re: Gap Determination (79 lines)
    From: Dave Brewer <david.brewer@UC.EDU>

  182. Re: eval the expression in variable (28 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  183. Re: eval the expression in variable (55 lines)
    From: Jim Groeneveld <jim.1stat@YAHOO.COM>

  184. Re: Using "call" function within PROC SQL ? (76 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  185. Re: column names only (36 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  186. Re: eval the expression in variable (78 lines)
    From: Jim Groeneveld <jim.1stat@YAHOO.COM>

  187. Re: Gap Determination (136 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  188. Automatic reply: Gap Determination (16 lines)
    From: McGuire, Joanmarie - Division of Assessment Design and Implementation <joanmarie.mcguire@EDUCATION.KY.GOV>

  189. Re: Better ways to put value into Macro variable during data step_side question added (195 lines)
    From: Bian, Haikuo <HBian@NW7.ESRD.NET>

  190. Re: eval the expression in variable (77 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  191. Re: File locking (96 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  192. Re: eval the expression in variable (62 lines)
    From: Chang Chung <chang_y_chung@HOTMAIL.COM>

  193. Confusing Dedup code (84 lines)
    From: Irin later <irinfigvam@YAHOO.COM>

  194. Re: Confusing Dedup code (124 lines)
    From: Irin later <irinfigvam@YAHOO.COM>

  195. Re: Confusing Dedup code (70 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  196. std deviation question (11 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  197. Re: Confusing Dedup code (122 lines)
    From: Irin later <irinfigvam@YAHOO.COM>

  198. Re: std deviation question (17 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  199. Call Lexcomb Question (20 lines)
    From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

  200. Re: eval the expression in variable (10 lines)
    From: Clark An <kuhasu@126.COM>

  201. Re: eval the expression in variable (36 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  202. Re: std deviation question (26 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  203. Re: eval the expression in variable (28 lines)
    From: Clark An <kuhasu@126.COM>

  204. Re: std deviation question (28 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  205. Re: eval the expression in variable (7 lines)
    From: Clark An <kuhasu@126.COM>

  206. Re: Confusing Dedup code (21 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  207. Re: std deviation question (40 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  208. Re: Confusing Dedup code (39 lines)
    From: Irin later <irinfigvam@YAHOO.COM>

  209. Re: eval the expression in variable (32 lines)
    From: Clark An <kuhasu@126.COM>

  210. Re: std deviation question (34 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  211. Re: std deviation question (54 lines)
    From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>

  212. Re: Confusing Dedup code (111 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  213. PROC MIXED-Repeated measures Covariance Structure (31 lines)
    From: James Algina <algina@UFL.EDU>

  214. Re: Confusing Dedup code (163 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  215. Re: Confusing Dedup code (79 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  216. Re: Call Lexcomb Question (88 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  217. Re: Call Lexcomb Question (100 lines)
    From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

  218. Re: std deviation question (106 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  219. Re: eval the expression in variable (53 lines)
    From: Clark An <kuhasu@126.COM>

  220. Re: eval the expression in variable (18 lines)
    From: Clark An <kuhasu@126.COM>

  221. Re: Confusing Dedup code (245 lines)
    From: Irin later <irinfigvam@YAHOO.COM>

  222. Re: std deviation question (118 lines)
    From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>

  223. Re: PROC MIXED-Repeated measures Covariance Structure (89 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  224. sampsize statement in PROC SURVEYSELECT...though this may be a macro question (38 lines)
    From: Randall Powers <powers_r@BLS.GOV>

  225. Re: std deviation question (171 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  226. Re: PROC MIXED-Repeated measures Covariance Structure (52 lines)
    From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>

  227. Re: sampsize statement in PROC SURVEYSELECT...though this may be a macro question (101 lines)
    From: Jack Clark <jclark@HILLTOP.UMBC.EDU>

  228. Re: Confusing Dedup code (253 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  229. Re: eval the expression in variable (91 lines)
    From: Clark An <kuhasu@126.COM>

  230. Re: sampsize statement in PROC SURVEYSELECT...though this may be a macro question (74 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  231. Re: eval the expression in variable (172 lines)
    From: oloolo <dynamicpanel@YAHOO.COM>

  232. Re: PROC MIXED-Repeated measures Covariance Structure (148 lines)
    From: Robin R High <rhigh@UNMC.EDU>

  233. Automatic reply: PROC MIXED-Repeated measures Covariance Structure (11 lines)
    From: Rick Smith <Ricky_L_Smith@DELL.COM>

  234. Re: PROC MIXED-Repeated measures Covariance Structure (209 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  235. Using Templates with Proc Greplay (24 lines)
    From: Dave Cannon <cannondj@AOL.COM>

  236. Re: Using Templates with Proc Greplay (38 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  237. ERROR: Index TEMPINDX cannot be created (34 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  238. Re: ERROR: Index TEMPINDX cannot be created (51 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  239. Re: ERROR: Index TEMPINDX cannot be created (69 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  240. Estimate Statement - Cell Sample Size Consideration (53 lines)
    From: R B <ryan.andrew.black@GMAIL.COM>

  241. Re: eval the expression in variable (193 lines)
    From: Clark An <kuhasu@126.COM>

  242. How to get the data set id when the data set has been openned? (24 lines)
    From: Clark An <kuhasu@126.COM>

  243. Re: eval the expression in variable (52 lines)
    From: Chang Chung <chang_y_chung@HOTMAIL.COM>

  244. Re: eval the expression in variable (63 lines)
    From: Clark An <kuhasu@126.COM>

  245. Re: eval the expression in variable (84 lines)
    From: Clark An <kuhasu@126.COM>

  246. Re: replacing var name with label in multiway list format (66 lines)
    From: Li Sun <sunli.judy@GMAIL.COM>

  247. Re: eval the expression in variable (15 lines)
    From: Clark An <kuhasu@126.COM>

  248. Re: Estimate Statement - Cell Sample Size Consideration (95 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  249. OT: manually code SQL for Excel (23 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  250. Re: Solution to "importing lots of txt files at once and taking the date from the title" (46 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  251. Re: eval the expression in variable (37 lines)
    From: Clark An <kuhasu@126.COM>

  252. Re: eval the expression in variable (197 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  253. how to treat consecutive delimiters as one when importing txt files (41 lines)
    From: Nuria Chapinal <nchapinal@YAHOO.COM>

  254. Re: how to treat consecutive delimiters as one when importing txt files (54 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  255. Re: eval the expression in variable (62 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  256. Re: how to treat consecutive delimiters as one when importing txt files (92 lines)
    From: Núria Chapinal <nchapinal@YAHOO.COM>

  257. Re: Estimate Statement - Cell Sample Size Consideration (154 lines)
    From: R B <ryan.andrew.black@GMAIL.COM>

  258. Re: eval the expression in variable (20 lines)
    From: Clark An <kuhasu@126.COM>

  259. Re: OT: manually code SQL for Excel (32 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  260. Re: eval the expression in variable (41 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  261. Re: eval the expression in variable (46 lines)
    From: Clark An <kuhasu@126.COM>

  262. Re: eval the expression in variable (57 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  263. Re: how to treat consecutive delimiters as one when importing txt files (108 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  264. Re: how to treat consecutive delimiters as one when importing txt files (123 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  265. Re: MIME: multipart/alternative with different plain and html content (48 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  266. Re: Confusing Dedup code (357 lines)
    From: Irin later <irinfigvam@YAHOO.COM>

  267. Re: how to treat consecutive delimiters as one when importing txt files (171 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  268. Re: eval the expression in variable (57 lines)
    From: Clark An <kuhasu@126.COM>

  269. Re: proc contents (311 lines)
    From: Li Sun <sunli.judy@GMAIL.COM>

  270. Re: eval the expression in variable (152 lines)
    From: Clark An <kuhasu@126.COM>

  271. Re: eval the expression in variable (52 lines)
    From: Clark An <kuhasu@126.COM>

  272. Re: eval the expression in variable (23 lines)
    From: Clark An <kuhasu@126.COM>

  273. Re: math expression problem in PROC GA (139 lines)
    From: Richard DeVenezia <rdevenezia@GMAIL.COM>

  274. Re: how to treat consecutive delimiters as one when importing txt files (209 lines)
    From: Núria Chapinal <nchapinal@YAHOO.COM>

  275. Re: how to treat consecutive delimiters as one when importing txt files (237 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  276. Re: how to treat consecutive delimiters as one when importing txt files (258 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  277. Re: proc contents (350 lines)
    From: Li Sun <sunli.judy@GMAIL.COM>

  278. Re: proc contents (39 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  279. proc panel output (31 lines)
    From: Anna Tsui <ascui@UIC.EDU>

  280. Re: proc panel output (54 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  281. Coalesce (56 lines)
    From: Randy <randistan69@HOTMAIL.COM>

  282. Re: Coalesce (99 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  283. Re: Coalesce (83 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  284. Re: Coalesce (11 lines)
    From: Randy <randistan69@HOTMAIL.COM>

  285. Proc SQL Left join (25 lines)
    From: Katrin Kin <katrina022509@YAHOO.COM>

  286. Re: Proc SQL Left join (65 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  287. Re: Coalesce (36 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  288. Re: Estimate Statement - Cell Sample Size Consideration (279 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  289. Re: Coalesce (91 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  290. FORECAST-- help (31 lines)
    From: Pradeep <chittiprolupradeep@GMAIL.COM>

  291. Re: FORECAST-- help (53 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  292. Reading Linux files from a Windows server (24 lines)
    From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM>

  293. Re: Reading Linux files from a Windows server (33 lines)
    From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

  294. Re: Reading Linux files from a Windows server (51 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  295. Re: proc contents (14 lines)
    From: Jim Groeneveld <jim.1stat@YAHOO.COM>

  296. Experiencing viidb issue (55 lines)
    From: Schwartz, Alan <Alan.Schwartz@ACS-INC.COM>

  297. Re: Estimate Statement - Cell Sample Size Consideration (286 lines)
    From: R B <ryan.andrew.black@GMAIL.COM>

  298. Re: Reading Linux files from a Windows server (60 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  299. Re: Reading Linux files from a Windows server (90 lines)
    From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>

  300. Re: Proc SQL Left join (87 lines)
    From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>

  301. Re: Proc Sort nodupkey for all columns (211 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  302. How to solve this senario? (22 lines)
    From: Nway <hymadsk@GMAIL.COM>

  303. Re: How to get the data set id when the data set has been openned? (49 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  304. Re: FORECAST-- help (45 lines)
    From: Tansu TOSUN <tansutosun@GMAIL.COM>

  305. Generating Two Random (Different) Numbers (14 lines)
    From: Eduardo Galvan <egalvan@ISR.UMICH.EDU>

  306. Re: Generating Two Random (Different) Numbers (28 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  307. Re: Generating Two Random (Different) Numbers (61 lines)
    From: Jordan, Lewis <Lewis.Jordan@WEYERHAEUSER.COM>

  308. Re: Generating Two Random (Different) Numbers (56 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  309. Re: How to solve this senario? (39 lines)
    From: Jim Groeneveld <jim.1stat@YAHOO.COM>

  310. Relative path names in view (35 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  311. Create a one-record dataset based on an empty data (34 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  312. Re: Create a one-record dataset based on an empty data (48 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  313. Re: Create a one-record dataset based on an empty data (48 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  314. Re: Create a one-record dataset based on an empty data (56 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  315. Re: Create a one-record dataset based on an empty data (49 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  316. Re: Create a one-record dataset based on an empty data (69 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  317. Re: Generating Two Random (Different) Numbers (93 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  318. Re: Create a one-record dataset based on an empty data (55 lines)
    From: Paul Dorfman <sashole@BELLSOUTH.NET>

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