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 – May 2012, week 3

  1. Re: 90 instances of SAS display manager (33 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  2. Re: 90 instances of SAS display manager (46 lines)
    From: Peter Timusk <petertimusk@PROGRAMDOCUMENTATION.COM>

  3. Re: 90 instances of SAS display manager (35 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  4. 90 instances of SAS display manager (13 lines)
    From: Peter Timusk <petertimusk@PROGRAMDOCUMENTATION.COM>

  5. Re: For each obs, find the variable that contains the min value (95 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  6. Re: PROC REPORT: Change Background Color for Cells with Non-Missing Data Without Specifying Variable Names (93 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  7. Re: transparency background (37 lines)
    From: Zdeb, Michael S <mzdeb@ALBANY.EDU>

  8. Re: PROC REPORT: Change Background Color for Cells with Non-Missing Data Without Specifying Variable Names (143 lines)
    From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>

  9. Re: PROC REPORT: Change Background Color for Cells with Non-Missing Data Without Specifying Variable Names (105 lines)
    From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>

  10. PROC REPORT: Change Background Color for Cells with Non-Missing Data Without Specifying Variable Names (84 lines)
    From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>

  11. Re: where also statement (96 lines)
    From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>

  12. Re: transparency background (43 lines)
    From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>

  13. Re: Proc SQL efficiency help needed (13 lines)
    From: Sigurd W. Hermansen <hermans1@WESTAT.COM>

  14. Re: transparency background (21 lines)
    From: Ben <benpub7@YAHOO.COM>

  15. Re: Proc SQL efficiency help needed (83 lines)
    From: DUELL, BOB <bd9439@ATT.COM>

  16. Workshop: R for SAS, SPSS, Stata Users (29 lines)
    From: Muenchen, Robert A (Bob) <muenchen@UTK.EDU>

  17. Re: Proc SQL efficiency help needed (121 lines)
    From: Tolbert, William <tolbert.w@GHC.ORG>

  18. Re: Proc SQL efficiency help needed (52 lines)
    From: Sigurd W. Hermansen <hermans1@WESTAT.COM>

  19. Checking memory use by a SAS process (30 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  20. Re: creating superscript and subscript in SGPLOT (185 lines)
    From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

  21. Re: For each obs, find the variable that contains the min value (86 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  22. Re: Proc SQL efficiency help needed (75 lines)
    From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

  23. Re: For each obs, find the variable that contains the min value (37 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  24. Re: For each obs, find the variable that contains the min value (100 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  25. Re: For each obs, find the variable that contains the min value (91 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  26. Re: q values in logistic? (109 lines)
    From: Dennis Fisher <Dennis.Fisher@CSULB.EDU>

  27. Re: For each obs, find the variable that contains the min value (24 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  28. Re: For each obs, find the variable that contains the min value (73 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  29. Re: For each obs, find the variable that contains the min value (81 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  30. Re: q values in logistic? (87 lines)
    From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

  31. Re: For each obs, find the variable that contains the min value (67 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  32. Re: transparency background (7 lines)
    From: Ben <benpub7@YAHOO.COM>

  33. Re: q values in logistic? (59 lines)
    From: Dennis Fisher <Dennis.Fisher@CSULB.EDU>

  34. transparency background (14 lines)
    From: Ben <benpub7@YAHOO.COM>

  35. Re: For each obs, find the variable that contains the min value (37 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  36. OT: End of OLEDB on SQL Server (39 lines)
    From: Alan Churchill <savian.net@GMAIL.COM>

  37. Re: Proc SQL efficiency help needed (69 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  38. Proc SQL efficiency help needed (35 lines)
    From: Dave <david.brewer@UC.EDU>

  39. Re: For each obs, find the variable that contains the min value (54 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  40. For each obs, find the variable that contains the min value (17 lines)
    From: Rick Wicklin <Rick.Wicklin@SAS.COM>

  41. Automatic reply: How to change FONT in annotatation facility (14 lines)
    From: Hong Qin <HQin@MERKLEINC.COM>

  42. How to change FONT in annotatation facility (124 lines)
    From: SAS Analyst <analystprasad@YAHOO.CO.IN>

  43. Re: q values in logistic? (23 lines)
    From: Steve Denham <stevedrd@YAHOO.COM>

  44. Re: One Minute intervals (59 lines)
    From: Daniel Nordlund <djnordlund@FRONTIER.COM>

  45. Re: One Minute intervals (76 lines)
    From: Daniel Nordlund <djnordlund@FRONTIER.COM>

  46. Re: One Minute intervals (16 lines)
    From: James B <Osprey06@GMAIL.COM>

  47. Re: One Minute intervals (50 lines)
    From: Randy <randistan69@HOTMAIL.COM>

  48. Re: insert blanks (71 lines)
    From: Daniel Nordlund <djnordlund@FRONTIER.COM>

  49. Re: One Minute intervals (45 lines)
    From: Daniel Nordlund <djnordlund@FRONTIER.COM>

  50. Re: insert blanks (52 lines)
    From: Daniel Nordlund <djnordlund@FRONTIER.COM>

  51. One Minute intervals (19 lines)
    From: Randy <randistan69@HOTMAIL.COM>

  52. Re: creating superscript and subscript in SGPLOT (144 lines)
    From: Yu Zhang <zhangyu05@GMAIL.COM>

  53. Re: insert blanks (73 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  54. Re: creating superscript and subscript in SGPLOT (176 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  55. Re: creating superscript and subscript in SGPLOT (131 lines)
    From: Farmaha Bhupinder <bhupi80singh@YAHOO.CO.IN>

  56. Re: creating superscript and subscript in SGPLOT (53 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  57. creating superscript and subscript in SGPLOT (24 lines)
    From: Farmaha Bhupinder <bhupi80singh@YAHOO.CO.IN>

  58. Re: SAS as a Windows Service (44 lines)
    From: Alan Churchill <savian.net@GMAIL.COM>

  59. Re: where also statement (76 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  60. Re: where also statement (167 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  61. Re: where also statement (67 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  62. Re: where also statement (58 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  63. Re: Detecting the Windows date format (130 lines)
    From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

  64. Re: SAS as a Windows Service (64 lines)
    From: Michael Davis <michael@BASSETTCONSULTING.COM>

  65. q values in logistic? (21 lines)
    From: Dennis Fisher <Dennis.Fisher@CSULB.EDU>

  66. SAS as a Windows Service (15 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  67. Re: proc import causes crash (84 lines)
    From: Pirritano, Matthew J <PirritanoM@AETNA.COM>

  68. Re: Detecting the Windows date format (140 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  69. How do I change this PROC SQL code for SAS 9.3 (30 lines)
    From: Andrea Zimmerman <sassywench74va@GMAIL.COM>

  70. Re: insert blanks (107 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  71. Re: Detecting the Windows date format (124 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  72. Re: Detecting the Windows date format (122 lines)
    From: Joe DeShon <joedeshon@COMCAST.NET>

  73. Re: Detecting the Windows date format (90 lines)
    From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

  74. Re: proc import causes crash (86 lines)
    From: Pirritano, Matthew J <PirritanoM@AETNA.COM>

  75. Re: DEFINE INFINITE LOOP (100 lines)
    From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

  76. Re: glot - groups on the x axis (167 lines)
    From: Treder, David <dtreder@GENESEEISD.ORG>

  77. Re: proc import causes crash (67 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  78. Re: proc import causes crash (66 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  79. Re: DEFINE INFINITE LOOP (265 lines)
    From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

  80. Automatic reply: SAS-L Digest - 18 May 2012 - Special issue (#2012-368) (20 lines)
    From: Carol Olson <Carol.Olson@MEREDITH.COM>

  81. proc import causes crash (32 lines)
    From: Pirritano, Matthew J <PirritanoM@AETNA.COM>

  82. Re: Fw: DEFINE INFINITE LOOP (16 lines)
    From: Bin Zhu <bxz01@HEALTH.STATE.NY.US>

  83. Is there a benchmarking best practices sasCommunity.org article? (10 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  84. Re: glot - groups on the x axis (88 lines)
    From: Treder, David <dtreder@GENESEEISD.ORG>

  85. Re: glot - groups on the x axis (36 lines)
    From: High, Robin R <rhigh@UNMC.EDU>

  86. Re: Fw: DEFINE INFINITE LOOP (129 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  87. glot - groups on the x axis (17 lines)
    From: Treder, David <dtreder@GENESEEISD.ORG>

  88. P. Bourdages est absent (9 lines)
    From: Patrice Bourdages <patrice.bourdages@DGAG.CA>

  89. Re: DEFINE INFINITE LOOP (253 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  90. Re: Detecting the Windows date format (77 lines)
    From: Chris Hemedinger <Chris.Hemedinger@SAS.COM>

  91. Re: DEFINE INFINITE LOOP (32 lines)
    From: Bin Zhu <bxz01@HEALTH.STATE.NY.US>

  92. Re: insert blanks (90 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  93. Re: proc glimmix results output (77 lines)
    From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

  94. Re: proc glimmix results output (43 lines)
    From: Steve Denham <stevedrd@YAHOO.COM>

  95. Re: universal viewer 1.2 (9.3) (51 lines)
    From: Andre Wielki <wielki@INED.FR>

  96. proc glimmix results output (49 lines)
    From: Soumi <soumiray74@GMAIL.COM>

  97. Automatic reply: SAS-L Digest - 17 May 2012 to 18 May 2012 (#2012-367) (18 lines)
    From: Greg Yamashiro <gryamash@KSBE.EDU>

  98. Re: SAS Bug? Special characters & the end-of-file? (171 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  99. Re: SAS Bug? Special characters & the end-of-file? (161 lines)
    From: William W. Viergever <william@VIERGEVER.NET>

  100. Re: burn-in process in simulating time series data (30 lines)
    From: Rick Wicklin <Rick.Wicklin@SAS.COM>

  101. Re: datastep matching obs problem (174 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  102. Re: SAS Bug? Special characters & the end-of-file? (130 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  103. Re: insert blanks (97 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  104. Re: insert blanks (68 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  105. Re: SAS Bug? Special characters & the end-of-file? (95 lines)
    From: William W. Viergever <william@VIERGEVER.NET>

  106. Re: SAS Bug? Special characters & the end-of-file? (117 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  107. Re: SAS Bug? Special characters & the end-of-file? (93 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  108. Re: insert blanks (56 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  109. Re: SAS Bug? Special characters & the end-of-file? (73 lines)
    From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

  110. Re: DEFINE INFINITE LOOP (205 lines)
    From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

  111. Re: insert blanks (113 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  112. Re: Detecting the Windows date format (37 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  113. Re: Detecting the Windows date format (42 lines)
    From: Mark Miller <mdhmiller@GMAIL.COM>

  114. burn-in process in simulating time series data (20 lines)
    From: =?UTF-8?B?6aG+6aOe?= <gufei1984@GMAIL.COM>

  115. Re: Detecting the Windows date format (38 lines)
    From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV>

  116. Detecting the Windows date format (23 lines)
    From: Lorne Klassen <lk1@ROGERS.COM>

  117. Re: DEFINE INFINITE LOOP (156 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  118. Re: DEFINE INFINITE LOOP (123 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  119. Re: DEFINE INFINITE LOOP (86 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  120. Fw: DEFINE INFINITE LOOP (17 lines)
    From: Bin Zhu <bxz01@HEALTH.STATE.NY.US>

  121. Re: DEFINE INFINITE LOOP (75 lines)
    From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

  122. DEFINE INFINITE LOOP (48 lines)
    From: Bin Zhu <bxz01@HEALTH.STATE.NY.US>

  123. Re: datastep matching obs problem (122 lines)
    From: J <jdiebal@GMAIL.COM>

  124. Analytic job openings available in exciting new area within healthcare: Payment Innovation (43 lines)
    From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM>

  125. helps for MySQL/ODBC (38 lines)
    From: Hong Yang <hong.yang550@GMAIL.COM>

  126. SAS Bug? Special characters & the end-of-file? (58 lines)
    From: Paul Hamilton <pdhamilton1@COMCAST.NET>

  127. Automatic reply: insert blanks (22 lines)
    From: Mahometa, Michael J <michael.mahometa@SSC.UTEXAS.EDU>

  128. Re: insert blanks (101 lines)
    From: Daniel Nordlund <djnordlund@FRONTIER.COM>

  129. Re: SAS Bug? Special characters & the end-of-file? (116 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  130. Re: insert blanks (85 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  131. Re: SAS Bug? Special characters & the end-of-file? (104 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  132. Re: SAS Bug? Special characters & the end-of-file? (104 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  133. Re: SAS Bug? Special characters & the end-of-file? (94 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  134. Re: SAS Bug? Special characters & the end-of-file? (86 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  135. Re: SAS Bug? Special characters & the end-of-file? (81 lines)
    From: Paul Hamilton <pdhamilton1@COMCAST.NET>

  136. Re: SAS Bug? Special characters & the end-of-file? (79 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  137. SAS Bug? Special characters & the end-of-file? (63 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  138. Re: strange behavior of code (293 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  139. Re: datastep matching obs problem (121 lines)
    From: JD <jdiebal@GMAIL.COM>

  140. Re: datastep matching obs problem (73 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  141. datastep matching obs problem (35 lines)
    From: JD <jdiebal@GMAIL.COM>

  142. Re: insert blanks (72 lines)
    From: Ken Borowiak <evilpettingzoo97@AOL.COM>

  143. SAS Stored Processes: 3 Tips to Improve Your Prompts (13 lines)
    From: Vincent Granville <vincentg@DATASHAPING.COM>

  144. Re: strange behavior of code (290 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  145. Re: universal viewer 1.2 (9.3) (69 lines)
    From: Arthur Tabachneck <art297@ROGERS.COM>

  146. Re: proc sql question (52 lines)
    From: Yu Zhang <zhangyu05@GMAIL.COM>

  147. Re: strange behavior of code (271 lines)
    From: DUELL, BOB <bd9439@ATT.COM>

  148. proc sql question (35 lines)
    From: Masoud Pajoh <mpajoh@ODOT.ORG>

  149. Re: Upper and Lower degrees of freedom (189 lines)
    From: SAS_learner <proccontents@GMAIL.COM>

  150. Re: strange behavior of code (255 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  151. Re: using tranwrd to eliminate substrings (144 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  152. Re: using tranwrd to eliminate substrings (136 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  153. Re: using tranwrd to eliminate substrings (113 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  154. Re: using tranwrd to eliminate substrings (96 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  155. Re: using tranwrd to eliminate substrings (70 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  156. Re: using tranwrd to eliminate substrings (65 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  157. Re: using tranwrd to eliminate substrings (89 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  158. Re: using tranwrd to eliminate substrings (81 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  159. Re: using tranwrd to eliminate substrings (65 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  160. using tranwrd to eliminate substrings (56 lines)
    From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

  161. Re: SAS random record selection (20 lines)
    From: oloolo <dynamicpanel@YAHOO.COM>

  162. SAS/CONNECT piping halts (466 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  163. Re: strange behavior of code (185 lines)
    From: DUELL, BOB <bd9439@ATT.COM>

  164. Re: strange behavior of code (176 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  165. Re: strange behavior of code (174 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  166. Bricolage Report: SQL Tricks (16 lines)
    From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV>

  167. Re: strange behavior of code (163 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  168. Re: strange behavior of code (158 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  169. Re: strange behavior of code (140 lines)
    From: DUELL, BOB <bd9439@ATT.COM>

  170. Re: Upper and Lower degrees of freedom (142 lines)
    From: SAS_learner <proccontents@GMAIL.COM>

  171. Re: strange behavior of code (142 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  172. Re: Macro to export to csv (52 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  173. Re: Macro to export to csv (34 lines)
    From: Burgess, Otto <OBurgess@ATPCO.NET>

  174. Re: strange behavior of code (8 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  175. Re: insert blanks (96 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  176. Re: strange behavior of code (116 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  177. Re: insert blanks (82 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

  178. Re: insert blanks (75 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  179. strange behavior of code (114 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  180. Re: insert blanks (44 lines)
    From: Yuewei Liu <contact@YUEWEILIU.COM>

  181. Re: insert blanks (37 lines)
    From: Fareeza Khurshed <fkhurshed@GMAIL.COM>

  182. insert blanks (29 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  183. Re: Upper and Lower degrees of freedom (93 lines)
    From: Bhupinder Singh Farmaha <bhupi80singh@YAHOO.CO.IN>

  184. Re: how to deal with invalid data when reading large raw data (327 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  185. Re: Macro to export to csv (20 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  186. Re: Upper and Lower degrees of freedom (76 lines)
    From: SAS_learner <proccontents@GMAIL.COM>

  187. Re: Upper and Lower degrees of freedom (70 lines)
    From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>

  188. Re: how to deal with invalid data when reading large raw data (112 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  189. Upper and Lower degrees of freedom (53 lines)
    From: SAS_learner <proccontents@GMAIL.COM>

  190. Re: Extract id's with multiple (84 lines)
    From: Asante, Abena <Abena.Asante@CIBC.COM>

  191. 2 SAS Professionals Needed Immediately For Contract Work--Rates $100+/Hour (119 lines)
    From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

  192. Re: Extract id's with multiple (81 lines)
    From: Doug Fuller <doug.fuller@ARBORRESEARCH.ORG>

  193. Re: Extract id's with multiple (73 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  194. Re: Extract id's with multiple (16 lines)
    From: Kim Brown <kibrown@LADHS.ORG>

  195. Re: Extract id's with multiple (22 lines)
    From: Peterson, Stephanie M. [RO HCPR] <Peterson.Stephanie2@MAYO.EDU>

  196. Re: Extract id's with multiple (74 lines)
    From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US>

  197. Extract id's with multiple (37 lines)
    From: Asante, Abena <Abena.Asante@CIBC.COM>

  198. Re: How to extract a date variable with where condition (100 lines)
    From: Mirisage Fernando <neilfrnnd@GMAIL.COM>

  199. Re: How to extract a date variable with where condition (77 lines)
    From: Mirisage Fernando <neilfrnnd@GMAIL.COM>

  200. Re: How to extract a date variable with where condition (89 lines)
    From: MAHESH <peesari.mahesh@GMAIL.COM>

  201. Re: How to extract a date variable with where condition (68 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  202. How to extract a date variable with where condition (56 lines)
    From: Mirisage Fernando <neilfrnnd@GMAIL.COM>

  203. Re: SAS random record selection (28 lines)
    From: Rick Wicklin <Rick.Wicklin@SAS.COM>

  204. Re: how to deal with invalid data when reading large raw data (308 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  205. Re: how to deal with invalid data when reading large raw data (287 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  206. Re: SAS random record selection (75 lines)
    From: Mary <mlhoward@AVALON.NET>

  207. SAS to ECL conversion (15 lines)
    From: polyphonic48@gmail.com <polyphonic48@GMAIL.COM>

  208. Re: SAS random record selection (46 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  209. Re: SAS random record selection (29 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  210. Re: how to deal with invalid data when reading large raw data (265 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  211. Re: how to deal with invalid data when reading large raw data (234 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  212. Re: Macro to export to csv (15 lines)
    From: Jerome <jerome.masset@CEGEDIM.FR>

  213. Re: how to deal with invalid data when reading large raw data (193 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  214. SAS random record selection (15 lines)
    From: Kathleen Askland <k.askland@GMAIL.COM>

  215. Re: how to deal with invalid data when reading large raw data (118 lines)
    From: bbser 2009 <bbser2009@GMAIL.COM>

  216. Re: Macro to export to csv (64 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  217. Macro to export to csv (24 lines)
    From: Randy <randistan69@HOTMAIL.COM>

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

  219. Re: SAS random record selection (57 lines)
    From: Mary <mlhoward@AVALON.NET>

  220. Re: Q: need to nest PDF bookmarks (99 lines)
    From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

  221. SAS random record selection (13 lines)
    From: Kathleen Askland <k.askland@GMAIL.COM>

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

  223. Re: Q: need to nest PDF bookmarks (24 lines)
    From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

  224. universal viewer 1.2 (9.3) (53 lines)
    From: Andre Wielki <wielki@INED.FR>

  225. Re: how to deal with invalid data when reading large raw data (66 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  226. Re: how to touch triangle symbol exactly below BAR (69 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

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

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

  229. how to touch triangle symbol exactly below BAR (52 lines)
    From: SAS Analyst <analystprasad@YAHOO.CO.IN>

  230. I need Gradient color shading in red,yellow and green sas annotation facility (34 lines)
    From: SAS Analyst <analystprasad@YAHOO.CO.IN>

  231. Automatic reply: SAS-L Digest - 14 May 2012 to 15 May 2012 (#2012-354) (28 lines)
    From: Gruver, Deena <dgruver@GERON.COM>

  232. Automatic reply: SAS-L Digest - 14 May 2012 to 15 May 2012 (#2012-354) (18 lines)
    From: Greg Yamashiro <gryamash@KSBE.EDU>

Back to the main SAS-L page