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 2

  1. Re: censored independent variable? (50 lines)
    From: Xin Wei <xinwei@STAT.PSU.EDU>

  2. problems with locks on stored macros (31 lines)
    From: White, Svend A. <SvendW@HEALTH.OK.GOV>

  3. Re: calling WinZip to zip output data from a SAS program (51 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  4. Re: import then export but get different result?? (240 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  5. calling WinZip to zip output data from a SAS program (39 lines)
    From: Burton, Ray <Ray.Burton@ACS-INC.COM>

  6. Re: A Format quesion - Urgent (35 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  7. FICO Webinar: Boost Insurance Underwriting Accuracy with Predictive Analytics (39 lines)
    From: Vincent Granville <vincentg@DATASHAPING.COM>

  8. A Format quesion - Urgent (24 lines)
    From: Tom Smith <need_sas_help@YAHOO.COM>

  9. How to model this? (23 lines)
    From: Sphinx Verdant <verdantsphinx@GMAIL.COM>

  10. Re: import then export but get different result?? (194 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  11. Automatic reply: SAS-L Digest - 13 Jun 2011 to 14 Jun 2011 - Special issue (#2011-599) (12 lines)
    From: Erika Steinmetz <esteinmetz@AAMC.ORG>

  12. Re: import then export but get different result?? (229 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  13. OT, UE to find Unicode: 0x0 ? (17 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  14. Re: INPUT oddity (44 lines)
    From: Ben <benpub7@YAHOO.COM>

  15. import then export but get different result?? (161 lines)
    From: Alex Tang <Alex.Tang@CREDITONE.COM>

  16. Re: quotation doubled when exporting? (167 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  17. Re: censored independent variable? (50 lines)
    From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>

  18. Automatic reply: [SAS-L] PROC SGPLOT graphs not opening (21 lines)
    From: Aminova, Frida <faminova@PACE.EDU>

  19. PROC SGPLOT graphs not opening (26 lines)
    From: Chris Bat <darth.pathos@GMAIL.COM>

  20. $90 discount if you register for Clinical Trial Analysis Using R before June 17th (398 lines)
    From: Dorothy Middleton <courses@STATCOURSE.COM>

  21. Re: Historical note - Univac 1 (129 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  22. Re: Historical note - Univac 1 (117 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  23. Re: quotation doubled when exporting? (104 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  24. Re: quotation doubled when exporting? (92 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  25. quotation doubled when exporting? (71 lines)
    From: Alex Tang <Alex.Tang@CREDITONE.COM>

  26. SAS IML Error: Segmentation Violation In Task [ IML (2) ] (59 lines)
    From: Robert Feyerharm <rfeyerha@TRAVELERS.COM>

  27. Re: INPUT oddity (25 lines)
    From: Jeff J. Voeller <SAS-Programmer@WYWH.COM>

  28. Re: Random coefficient mixed model (48 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  29. Random coefficient mixed model (22 lines)
    From: Sphinx Verdant <verdantsphinx@GMAIL.COM>

  30. Re: censored independent variable? (37 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  31. Re: Proc datasets and Oracle error (127 lines)
    From: Carol Bristow <Carol.Bristow@DPRA.COM>

  32. Re: INPUT oddity (54 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  33. INPUT oddity (42 lines)
    From: Jeff J. Voeller <SAS-Programmer@WYWH.COM>

  34. Re: Proc datasets and Oracle error (99 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  35. Automatic reply: why we need "stop;" preceding "run;" ? (19 lines)
    From: Jan Squillace <Jan.Squillace@SAS.COM>

  36. Re: Proc datasets and Oracle error (80 lines)
    From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>

  37. Re: why we need "stop;" preceding "run;" ? (133 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  38. Re: why we need "stop;" preceding "run;" ? (107 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  39. Proc datasets and Oracle error (48 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  40. Re: Historical note - Univac 1 (66 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  41. Re: Historical note - Univac 1 (60 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  42. Re: Historical note - Univac 1 (57 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  43. Re: Historical note - Univac 1 (40 lines)
    From: Kirby, Ted <ted.kirby@LEWIN.COM>

  44. Re: Can one determine pixel length of a string? (148 lines)
    From: Murphy Choy <goladin@GMAIL.COM>

  45. Re: Can one determine pixel length of a string? (116 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  46. Re: Can one determine pixel length of a string? (86 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  47. Re: Validating multiple date formats and SAS test data entry (91 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  48. Re: Can one determine pixel length of a string? (63 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  49. Re: Can one determine pixel length of a string? (35 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  50. Re: Can one determine pixel length of a string? (25 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  51. Can one determine pixel length of a string? (12 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  52. Historical note - Univac 1 (16 lines)
    From: Hoyle, Larry <larryhoyle@KU.EDU>

  53. Validating multiple date formats and SAS test data entry (36 lines)
    From: Brian Wallace <brian_c_wallace@YAHOO.COM>

  54. Re: row-level vs column-level SUM in proc sql (96 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  55. Re: row-level vs column-level SUM in proc sql (88 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  56. Re: why we need "stop;" preceding "run;" ? (86 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  57. Re: why we need "stop;" preceding "run;" ? (56 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  58. Re: why we need "stop;" preceding "run;" ? (74 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  59. Re: why we need "stop;" preceding "run;" ? (79 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  60. Re: Chance to Make SAS-L History: Did You Know That... (135 lines)
    From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

  61. Re: GLIMMIX LSMEANS PLOT: WANT A common y axis with by statement (37 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  62. GLIMMIX LSMEANS PLOT: WANT A common y axis with by statement (87 lines)
    From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU>

  63. Re: Chance to Make SAS-L History: Did You Know That... (76 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  64. censored independent variable? (11 lines)
    From: Xin Wei <xinwei@STAT.PSU.EDU>

  65. Online Summer Courses Using R Software (71 lines)
    From: Geoffrey Hubona <ghubona@GMAIL.COM>

  66. why we need "stop;" preceding "run;" ? (41 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  67. Re: Macro to write to external file (18 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  68. Re: Macro to write to external file (311 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  69. Re: Macro to write to external file (294 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  70. Re: Macro to write to external file (265 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  71. Re: Macro to write to external file (277 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  72. Re: Macro to write to external file (252 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  73. Re: Macro to write to external file (261 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  74. Re: Macro to write to external file (243 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  75. Re: Macro to write to external file (80 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  76. Re: Macro to write to external file (243 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  77. Re: Macro to write to external file (225 lines)
    From: MAHESH <peesari.mahesh@GMAIL.COM>

  78. Re: Macro to write to external file (196 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  79. Re: Macro to write to external file (147 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  80. Re: Macro to write to external file (110 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  81. Re: Macro to write to external file (97 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  82. Re: Macro to write to external file (116 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  83. Re: Macro to write to external file (58 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  84. Re: Macro to write to external file (79 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  85. Macro to write to external file (37 lines)
    From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM>

  86. Re: SAS OR and ETS (50 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  87. Re: SAS OR and ETS (48 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  88. Re: SAS OR and ETS (37 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  89. Re: SAS OR and ETS (22 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  90. Re: SAS OR and ETS (76 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  91. Re: locking issues with view (59 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  92. Re: IS8601TM (102 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  93. Re: IS8601TM (60 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  94. Re: How to Add Prior Month Totals in PROC REPORT (39 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  95. How to Add Prior Month Totals in PROC REPORT (27 lines)
    From: jack quin <qinlixun@GMAIL.COM>

  96. Re: Sas Date Conversion (37 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  97. Re: Sas Date Conversion (32 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  98. Re: IS8601TM (88 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  99. Re: Sas Date Conversion (50 lines)
    From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>

  100. Re: Connect Local SAS to a SAS Server (71 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  101. Re: row-level vs column-level SUM in proc sql (69 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  102. Re: row-level vs column-level SUM in proc sql (56 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  103. Connect Local SAS to a SAS Server (44 lines)
    From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

  104. Re: Sas Date Conversion (88 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  105. row-level vs column-level SUM in proc sql (50 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  106. Re: General math-ish type help - PCA and Cluster Analysis (39 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  107. General math-ish type help - PCA and Cluster Analysis (21 lines)
    From: Chris Bat <darth.pathos@GMAIL.COM>

  108. Re: IS8601TM (53 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  109. Re: Sas Date Conversion (77 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  110. Re: Automatic reply: SAS-L Digest - 10 Jun 2011 - Special issue (#2011-589) (36 lines)
    From: F J Kelley <jkelley@UGA.EDU>

  111. Re: Automatic reply: SAS-L Digest - 10 Jun 2011 - Special issue (#2011-589) (28 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  112. Automatic reply: SAS-L Digest - 10 Jun 2011 - Special issue (#2011-589) (21 lines)
    From: Carol Olson <Carol.Olson@MEREDITH.COM>

  113. Automatic reply: SAS-L Digest - 10 Jun 2011 - Special issue (#2011-589) (15 lines)
    From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU>

  114. Re: Best practices question: connecting to Oracle databases via SAS (86 lines)
    From: Muhammad Sohail <sohailbme@GMAIL.COM>

  115. Re: Sas Date Conversion (61 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  116. Re: SAS report to Web and Web query to SAS (60 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  117. Re: Sas Date Conversion (69 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  118. Re: Bootstrap Logistic Regression (36 lines)
    From: R B <ryan.andrew.black@GMAIL.COM>

  119. Bootstrap Logistic Regression (44 lines)
    From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

  120. Re: Sas Date Conversion (79 lines)
    From: Adams, Nicholas <NRAdams@CVTY.COM>

  121. Re: Sas Date Conversion (54 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  122. Re: Sas Date Conversion (87 lines)
    From: Jack Clark <jclark@HILLTOP.UMBC.EDU>

  123. Sas Date Conversion (43 lines)
    From: Adams, Nicholas <NRAdams@CVTY.COM>

  124. Re: SAS 9.3? (35 lines)
    From: oloolo <dynamicpanel@YAHOO.COM>

  125. Re: SAS 9.3? (38 lines)
    From: F J Kelley <jkelley@UGA.EDU>

  126. Re: SAS 9.3? (28 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  127. SAS 9.3? (12 lines)
    From: F J Kelley <jkelley@UGA.EDU>

  128. Re: tukey test (48 lines)
    From: Jerry Davis <jwd@UGA.EDU>

  129. ods (30 lines)
    From: Huaandrew <andrew0845@HOTMAIL.COM>

  130. Re: automatically collect all variable names of a data set (27 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  131. OT: Friday Humor (20 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  132. Re: automatically collect all variable names of a data set (27 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  133. Re: Help in SAS- Insurance Domain (23 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  134. Help in SAS- Insurance Domain (13 lines)
    From: Vishali Rajiv <vishalirajiv@YAHOO.COM>

  135. Re: automatically collect all variable names of a data set (40 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  136. Re: automatically collect all variable names of a data set (40 lines)
    From: John Hendrickx <john2.hendrickx@GMAIL.COM>

  137. automatically collect all variable names of a data set (19 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  138. tukey test (84 lines)
    From: Johanna Griffin <jkgriffin@UCDAVIS.EDU>

  139. Re: "Row title space too small to print titles for the table statement" error (103 lines)
    From: White, Svend A. <SvendW@HEALTH.OK.GOV>

  140. Re: "Row title space too small to print titles for the table statement" error (101 lines)
    From: White, Svend A. <SvendW@HEALTH.OK.GOV>

  141. Re: "Row title space too small to print titles for the table statement" error (74 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  142. "Row title space too small to print titles for the table statement" error (66 lines)
    From: White, Svend A. <SvendW@HEALTH.OK.GOV>

  143. Re: SAS connection to SQL Server (39 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  144. SAS connection to SQL Server (26 lines)
    From: Gordon Keeler <gkeeler@PSYCH.DUHS.DUKE.EDU>

  145. quiet install (34 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  146. Re: IS8601TM (166 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  147. Re: IS8601TM (150 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  148. Re: IS8601TM (34 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  149. Re: IS8601TM (137 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  150. Re: IS8601TM (20 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  151. Re: IS8601TM (13 lines)
    From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM>

  152. Re: IS8601TM (80 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  153. Re: IS8601TM (72 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  154. Re: SAS tip: SAS name literal variable names as argument (100 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  155. Re: An average question (64 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  156. Re: CSV file problem (65 lines)
    From: =?utf-8?B?15LXk9eZINeR158g15DXkdeZ?= <GADI_B@MALAM.COM>

  157. Re: IS8601TM (42 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  158. Re: creating Stored Process in Base SAS and EG and how to connect SP to IDP (42 lines)
    From: Murphy Choy <goladin@GMAIL.COM>

  159. creating Stored Process in Base SAS and EG and how to connect SP to IDP (19 lines)
    From: Pradeep <chittiprolupradeep@GMAIL.COM>

  160. IS8601TM (31 lines)
    From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM>

  161. Re: proc report (121 lines)
    From: Jim Groeneveld <jim.1stat@YAHOO.COM>

  162. SAS tip: SAS name literal variable names as argument (69 lines)
    From: Jim Groeneveld <jim.1stat@YAHOO.COM>

  163. Re: proc report (128 lines)
    From: John Mike <sasslick@GMAIL.COM>

  164. Re: proc report (118 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  165. Automatische Antwort: proc report (15 lines)
    From: Sascha Räuschel <Sascha.Raeuschel@GER.SAS.COM>

  166. proc report (105 lines)
    From: John Mike <sasslick@GMAIL.COM>

  167. Re: Chance to Make SAS-L History: Did You Know That... (25 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  168. Re: An average question (36 lines)
    From: Steve Denham <stevedrd@YAHOO.COM>

  169. Starting Display Manager in 9.2 (33 lines)
    From: Joe DeShon <joedeshon@COMCAST.NET>

  170. Re: scanning a set of variables (40 lines)
    From: Sally Vegso <Sally.Vegso@YALE.EDU>

  171. Re: scanning a set of variables (84 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  172. Re: Chance to Make SAS-L History: Did You Know That... (130 lines)
    From: Kirby, Ted <ted.kirby@LEWIN.COM>

  173. Re: Long text fields in Excel (143 lines)
    From: Mike Rhoads <RHOADSM1@WESTAT.COM>

  174. Re: Exporting Facilities with Macro (12 lines)
    From: Kim Brown <kibrown@LADHS.ORG>

  175. Re: An average question (39 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  176. Re: scanning a set of variables (110 lines)
    From: Sally Vegso <Sally.Vegso@YALE.EDU>

  177. Re: scanning a set of variables (75 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  178. Re: scanning a set of variables (14 lines)
    From: Gabriel Rosas <rosas.gabe@GMAIL.COM>

  179. An average question (20 lines)
    From: Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>

  180. Re: scanning a set of variables (43 lines)
    From: Sally Vegso <Sally.Vegso@YALE.EDU>

  181. Re: scanning a set of variables (12 lines)
    From: Gabriel Rosas <rosas.gabe@GMAIL.COM>

  182. scanning a set of variables (49 lines)
    From: Sally Vegso <Sally.Vegso@YALE.EDU>

  183. Re: Chance to Make SAS-L History: Did You Know That... (126 lines)
    From: Bolotin Yevgeniy <ybolotin@SCHOOLS.NYC.GOV>

  184. Re: Chance to Make SAS-L History: Did You Know That... (103 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  185. Re: Strange symbol in SAS editor (40 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  186. Re: Strange symbol in SAS editor (87 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  187. Re: hard-coded hash object, what's wrong? (346 lines)
    From: Scott Bass <sas_l_739@YAHOO.COM.AU>

  188. Re: Thursday Theory (154 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  189. Re: Strange symbol in SAS editor (63 lines)
    From: John Hendrickx <john2.hendrickx@GMAIL.COM>

  190. AW: Thursday Theory (126 lines)
    From: Olaf Kruse <olaf.kruse@VST-GMBH.DE>

  191. Re: Chance to Make SAS-L History: Did You Know That... (110 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  192. Re: Request (69 lines)
    From: Vishali Rajiv <vishalirajiv@YAHOO.COM>

  193. Re: Strange symbol in SAS editor (32 lines)
    From: Ben <benpub7@YAHOO.COM>

  194. OT: Thursday Theory (87 lines)
    From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

  195. Re: type conversion; was: between operation (53 lines)
    From: Jim Groeneveld <jim.1stat@YAHOO.COM>

  196. Strange symbol in SAS editor (20 lines)
    From: John Hendrickx <john2.hendrickx@GMAIL.COM>

  197. Re: locking issues with view (36 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  198. Re: locking issues with view (31 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

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