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 2010, week 1

  1. Looking for advice on SAS and version control (26 lines)
    From: W. Matthew Wilson <matt@TPLUS1.COM>

  2. Finding the desktop without knowledge of the path structure (324 lines)
    From: Michael A McDaniel/AC/VCU <mamcdani@VCU.EDU>

  3. Re: Looking for advice on SAS and version control (59 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  4. Re: Finding the desktop without knowledge of the path structure (56 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  5. Re: Finding the desktop without knowledge of the path structure (43 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  6. admin: SAS Support Resources at Your Fingertips (30 lines)
    From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

  7. Hiring - SAS consultant for Pharma Business Analytics Group (35 lines)
    From: Alex Tsui <atsui.email@GMAIL.COM>

  8. Re: Looking for advice on SAS and version control (47 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  9. Re: Pulling dataset using dates ...... (85 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  10. Join SQL table with a SAS dataset? (51 lines)
    From: W. Matthew Wilson <matt@TPLUS1.COM>

  11. Re: Finding the desktop without knowledge of the path structure (54 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  12. Re: Join SQL table with a SAS dataset? (69 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  13. Re: Pulling dataset using dates ...... (124 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  14. Looking for replacement SSH Server for Reflection X (22 lines)
    From: Norman Weston <nweston@AMGEN.COM>

  15. Re: Join SQL table with a SAS dataset? (104 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  16. Re: Looking for advice on SAS and version control (41 lines)
    From: Anderson, James <James.Anderson@UCSF.EDU>

  17. Re: Looking for replacement SSH Server for Reflection X (42 lines)
    From: Wensui Liu <liuwensui@GMAIL.COM>

  18. Re: Looking for replacement SSH Server for Reflection X (60 lines)
    From: Michael Davis <michael@BASSETTCONSULTING.COM>

  19. autoexec.sas in the same location of batch run code and override the one in the folder of sas.exe? (21 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  20. Re: Looking for replacement SSH Server for Reflection X (60 lines)
    From: Wensui Liu <liuwensui@GMAIL.COM>

  21. Re: Looking for replacement SSH Server for Reflection X (12 lines)
    From: Norman Weston <nweston@AMGEN.COM>

  22. Re: autoexec.sas in the same location of batch run code and override the one in the folder of sas.exe? (72 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  23. Re: Pulling dataset using dates ...... (101 lines)
    From: Arthur Tabachneck <art297@NETSCAPE.NET>

  24. Re: SAS Reports (82 lines)
    From: saslearn chicago <sasswamy@GMAIL.COM>

  25. Re: Looking for replacement SSH Server for Reflection X (97 lines)
    From: WIELKI Andre <wielki@INED.FR>

  26. Analysis by Quarter (42 lines)
    From: Jack <mditconsult@GMAIL.COM>

  27. Re: Join SQL table with a SAS dataset? (74 lines)
    From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

  28. Re: Analysis by Quarter (91 lines)
    From: Pareen Patel <mditconsult@GMAIL.COM>

  29. Re: Excel LIBNAME Engine (22 lines)
    From: Arthur Tabachneck <art297@NETSCAPE.NET>

  30. Summarized & Comparison by Quarterly (66 lines)
    From: Pete <mditconsult@GMAIL.COM>

  31. Re: Retrieve host IP address (136 lines)
    From: Alan Churchill <alan.churchill@SAVIAN.NET>

  32. Re: Looking for advice on SAS and version control (61 lines)
    From: Alan Churchill <alan.churchill@SAVIAN.NET>

  33. Re: Finding the desktop without knowledge of the path structure (67 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  34. Reminder: Toronto Area SAS Society (TASS) June 2010 Meeting (72 lines)
    From: Arthur Tabachneck <art297@NETSCAPE.NET>

  35. Re: Finding the desktop without knowledge of the path structure (98 lines)
    From: Arthur Tabachneck <art297@NETSCAPE.NET>

  36. Re: Analysis by Quarter (85 lines)
    From: Ian Whitlock <iw1sas@GMAIL.COM>

  37. Re: Finding the desktop without knowledge of the path structure (105 lines)
    From: Arthur Tabachneck <art297@NETSCAPE.NET>

  38. Re: Finding the desktop without knowledge of the path structure (121 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  39. Re: Finding the desktop without knowledge of the path structure (81 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  40. Re: Finding the desktop without knowledge of the path structure (177 lines)
    From: Mark Miller <mdhmiller@GMAIL.COM>

  41. Infile/Cards strings with more than one space (175 lines)
    From: Sudo Ku <crafty876@HOTMAIL.COM>

  42. Re: Finding the desktop without knowledge of the path structure (176 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  43. Re: Finding the desktop without knowledge of the path structure (209 lines)
    From: Arthur Tabachneck <art297@NETSCAPE.NET>

  44. Re: Finding the desktop without knowledge of the path structure (227 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  45. Force Serialized Commit for Individual SQL Statements to OLE DB Table (65 lines)
    From: Kevin Myers <kmyers1@CLEARWIRE.NET>

  46. SAS SQL Delete Statement Bug with Microsoft Access Database (was: Force Serialized Commit for Individual SQL Statements to OLE DB Table) (95 lines)
    From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>

  47. Re: Force Serialized Commit for Individual SQL Statements to OLE DB Table (83 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  48. Edit check for the AE data (25 lines)
    From: Ravi <quicksilver_vcu@YAHOO.COM>

  49. Re: Force Serialized Commit for Individual SQL Statements to OLE DB Table (58 lines)
    From: Kevin Myers <kmyers1@CLEARWIRE.NET>

  50. Re: Force Serialized Commit for Individual SQL Statements to OLE DB Table (73 lines)
    From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>

  51. Fw: SAS Beginnings talk given by Tony Barr at NCSU on April 21, 2010. (48 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  52. SBC: Secure Baseline Configuration (21 lines)
    From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

  53. Re: Force Serialized Commit for Individual SQL Statements to OLE DB Table (110 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  54. Re: Edit check for the AE data (20 lines)
    From: Help <quicksilver_vcu@YAHOO.COM>

  55. Re: Edit check for the AE data (23 lines)
    From: Help <quicksilver_vcu@YAHOO.COM>

  56. RANDOM SAMPLING/PROC SURVEYSELECT (21 lines)
    From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM>

  57. Re: RANDOM SAMPLING/PROC SURVEYSELECT (46 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  58. Re: RANDOM SAMPLING/PROC SURVEYSELECT (87 lines)
    From: Mary <mlhoward@AVALON.NET>

  59. Re: RANDOM SAMPLING/PROC SURVEYSELECT (135 lines)
    From: oloolo <dynamicpanel@YAHOO.COM>

  60. Truncated axis values in HBAR (21 lines)
    From: Jennifer Fulton <jenniferfulton@WESTAT.COM>

  61. Running logcheck in batch mode (14 lines)
    From: Corey Duefield <cduefield@STAT.BROWN.EDU>

  62. Re: Force Serialized Commit for Individual SQL Statements to OLE DB Table (60 lines)
    From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>

  63. Re: Infile/Cards strings with more than one space (240 lines)
    From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

  64. Re: RANDOM SAMPLING/PROC SURVEYSELECT (101 lines)
    From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM>

  65. Re: RANDOM SAMPLING/PROC SURVEYSELECT (150 lines)
    From: Mary <mlhoward@AVALON.NET>

  66. Re: Edit check for the AE data (58 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  67. NLMIXED vs GLIMMIXED (31 lines)
    From: oslo <hokut1@YAHOO.COM>

  68. Re: Infile/Cards strings with more than one space (268 lines)
    From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

  69. Re: RANDOM SAMPLING/PROC SURVEYSELECT (159 lines)
    From: oloolo <dynamicpanel@YAHOO.COM>

  70. Re: Infile/Cards strings with more than one space (289 lines)
    From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

  71. Re: Running logcheck in batch mode (44 lines)
    From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

  72. Re: Infile/Cards strings with more than one space (346 lines)
    From: Sudo Ku <crafty876@HOTMAIL.COM>

  73. Re: Infile/Cards strings with more than one space (31 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  74. Re: NLMIXED vs GLIMMIXED (53 lines)
    From: oloolo <dynamicpanel@YAHOO.COM>

  75. Re: Pulling dataset using dates ...... (39 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  76. Re: Truncated axis values in HBAR (53 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  77. Re: NLMIXED vs GLIMMIXED (83 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  78. Re: Finding the desktop without knowledge of the path structure (66 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  79. Server estimate (51 lines)
    From: Viel, Kevin <kviel@SJHA.ORG>

  80. Re: NLMIXED vs GLIMMIXED (67 lines)
    From: Ryan Black <ryan.andrew.black@GMAIL.COM>

  81. Re: Server estimate (73 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  82. Re: NLMIXED vs GLIMMIXED (51 lines)
    From: oslo <hokut1@YAHOO.COM>

  83. Re: NLMIXED vs GLIMMIXED (67 lines)
    From: oslo <hokut1@YAHOO.COM>

  84. OT: Information Mapping Webinar: Structured Authoring (71 lines)
    From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

  85. Re: Server estimate (51 lines)
    From: Daniel Nordlund <djnordlund@VERIZON.NET>

  86. Re: Finding the desktop without knowledge of the path structure (107 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  87. Re: Finding the desktop without knowledge of the path structure (55 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  88. Error message in proc phreg (59 lines)
    From: Sarah Shannon <ster0171@UMN.EDU>

  89. I want to move SQL connection strings out of my SAS code (28 lines)
    From: W. Matthew Wilson <matt@TPLUS1.COM>

  90. Re: I want to move SQL connection strings out of my SAS code (45 lines)
    From: Joe Matise <snoopy369@GMAIL.COM>

  91. Re: I want to move SQL connection strings out of my SAS code (77 lines)
    From: Viel, Kevin <kviel@SJHA.ORG>

  92. Re: Error message in proc phreg (76 lines)
    From: Mary <mlhoward@AVALON.NET>

  93. Online Interactive Statistics Courses for July and August (63 lines)
    From: Dorothy Middleton <courses@STATCOURSE.COM>

  94. Re: Server estimate (63 lines)
    From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>

  95. Re: Retain and max() ?? (68 lines)
    From: Arthur Tabachneck <art297@NETSCAPE.NET>

  96. Re: SAS Reports (238 lines)
    From: saslearn chicago <sasswamy@GMAIL.COM>

  97. Re: Maximum Number of Weeks with a criteria (45 lines)
    From: Arthur Tabachneck <art297@NETSCAPE.NET>

  98. Re: Enterprise Guide 4.1/SAS 9.1.3 - How to disable LIBNAME statement (32 lines)
    From: Arthur Tabachneck <art297@NETSCAPE.NET>

  99. Quantreg procedure (25 lines)
    From: Kris <okie_dude2003@YAHOO.COM>

  100. Edit check (28 lines)
    From: Help <quicksilver_vcu@YAHOO.COM>

  101. Re: NLMIXED vs GLIMMIXED (234 lines)
    From: Ryan Black <ryan.andrew.black@GMAIL.COM>

  102. Is there a better way to calculate fiscal year? (32 lines)
    From: Dave Brewer <david.brewer@UC.EDU>

  103. Re: Is there a better way to calculate fiscal year? (49 lines)
    From: =?windows-1255?Q?=E2=E3=E9_=E1=EF_=E0=E1=E9?= <GADI_B@MALAM.COM>

  104. Using Weights in Proc Tabulate (28 lines)
    From: js8765 <js8765@GOOGLEMAIL.COM>

  105. Re: Using Weights in Proc Tabulate (35 lines)
    From: Arthur Tabachneck <art297@NETSCAPE.NET>

  106. Re: How to pass dataset variables' value to macro (70 lines)
    From: Arthur Tabachneck <art297@NETSCAPE.NET>

  107. Re: Is there a better way to calculate fiscal year? (63 lines)
    From: Dave Brewer <david.brewer@UC.EDU>

  108. Re: Is there a better way to calculate fiscal year? (156 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  109. Re: Is there a better way to calculate fiscal year? (54 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  110. Proc Tabulate (28 lines)
    From: Suren gc <gc_suren@YAHOO.COM>

  111. Re: Is there a better way to calculate fiscal year? (196 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  112. Explained: How to set up per-user autoexec.sas (41 lines)
    From: W. Matthew Wilson <matt@TPLUS1.COM>

  113. Windows 7 and SAS (25 lines)
    From: Catima Potter <cpotter@KUMC.EDU>

  114. Re: Error message in proc phreg (90 lines)
    From: Sarah Shannon <ster0171@UMN.EDU>

  115. Re: Edit check (48 lines)
    From: SAS_learner <proccontents@GMAIL.COM>

  116. Re: Explained: How to set up per-user autoexec.sas (68 lines)
    From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

  117. Re: Windows 7 and SAS (33 lines)
    From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

  118. Re: Proc Tabulate (54 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  119. Re: NLMIXED vs GLIMMIXED (289 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  120. Re: Server estimate (65 lines)
    From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

  121. Re: NLMIXED vs GLIMMIXED (121 lines)
    From: oslo <hokut1@YAHOO.COM>

  122. Re: Is there a better way to calculate fiscal year? (64 lines)
    From: Dave Brewer <david.brewer@UC.EDU>

  123. Re: NLMIXED vs GLIMMIX (38 lines)
    From: oslo <hokut1@YAHOO.COM>

  124. Trimming spaces on a put conversion to character? (17 lines)
    From: Mary <mlhoward@AVALON.NET>

  125. Re: Trimming spaces on a put conversion to character? (33 lines)
    From: Wensui Liu <liuwensui@GMAIL.COM>

  126. Re: Trimming spaces on a put conversion to character? (53 lines)
    From: Jack Clark <jclark@HILLTOP.UMBC.EDU>

  127. Re: Trimming spaces on a put conversion to character? (65 lines)
    From: Viel, Kevin <kviel@SJHA.ORG>

  128. Datetime format (17 lines)
    From: William Krause <wkrause2003@YAHOO.COM>

  129. Re: Trimming spaces on a put conversion to character? (49 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  130. Re: Trimming spaces on a put conversion to character? (77 lines)
    From: Mary <mlhoward@AVALON.NET>

  131. Hash Table to find lowest value (72 lines)
    From: Teed, Lionel <Lionel.Teed@TD.COM>

  132. Re: Datetime format (70 lines)
    From: Jack Clark <jclark@HILLTOP.UMBC.EDU>

  133. Re: NLMIXED vs GLIMMIX (138 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  134. Re: Online Interactive Statistics Courses for July and August (56 lines)
    From: Pashi, Arthur <Arthur.Pashi@DHSS.MO.GOV>

  135. Re: Datetime format (48 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  136. Re: Datetime format (79 lines)
    From: Viel, Kevin <kviel@SJHA.ORG>

  137. Re: Datetime format (45 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  138. Re: Datetime format (49 lines)
    From: Viel, Kevin <kviel@SJHA.ORG>

  139. Re: Trimming spaces on a put conversion to character? (87 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  140. PROC SQL Limitation in the number of expression when subsetting data using 'IN' statement. (133 lines)
    From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM>

  141. Couple of Question - CDF Plot (39 lines)
    From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM>

  142. Re: NLMIXED vs GLIMMIXED (163 lines)
    From: oslo <hokut1@YAHOO.COM>

  143. SAS oddities and spiders from Mars (51 lines)
    From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV>

  144. Re: SAS oddities and spiders from Mars (75 lines)
    From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

  145. Re: SAS oddities and spiders from Mars (58 lines)
    From: Data _null_; <iebupdte@GMAIL.COM>

  146. Re: SAS oddities and spiders from Mars (114 lines)
    From: Mike Zdeb <msz03@ALBANY.EDU>

  147. Re: I want to move SQL connection strings out of my SAS code (56 lines)
    From: Ian Whitlock <iw1sas@GMAIL.COM>

  148. Re: NLMIXED vs GLIMMIXED (138 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  149. Re: Hash Table to find lowest value (144 lines)
    From: Paul Dorfman <sashole@BELLSOUTH.NET>

  150. FW: Inquiry about SAS Macro (74 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  151. Re: NLMIXED vs GLIMMIXED (84 lines)
    From: oslo <hokut1@YAHOO.COM>

  152. Re: PROC SQL Limitation in the number of expression when subsetting data using 'IN' statement. (145 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  153. Re: I want to move SQL connection strings out of my SAS code (67 lines)
    From: Søren Lassen <s.lassen@POST.TELE.DK>

  154. Re: PROC SQL Limitation in the number of expression when subsetting data using 'IN' statement. (154 lines)
    From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

  155. Re: I want to move SQL connection strings out of my SAS code (40 lines)
    From: Jonas Bilenas <jonas.bilenas@CHASE.COM>

  156. Re: PROC SQL Limitation in the number of expression when subsetting data using 'IN' statement. (194 lines)
    From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM>

  157. Re: PROC SQL Limitation in the number of expression when subsetting data using 'IN' statement. (205 lines)
    From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM>

  158. Re: SAS oddities and spiders from Mars (88 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  159. Re: I want to move SQL connection strings out of my SAS code (58 lines)
    From: Michael Raithel <michaelraithel@WESTAT.COM>

  160. not getting plots in proc mixed results (29 lines)
    From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU>

  161. Re: Hash Table to find lowest value (113 lines)
    From: Teed, Lionel <Lionel.Teed@TD.COM>

  162. Re: not getting plots in proc mixed results (64 lines)
    From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM>

  163. Re: not getting plots in proc mixed results (41 lines)
    From: Ryan Black <ryan.andrew.black@GMAIL.COM>

  164. How to store t-stat in sas dataset form in proc autoreg ? (9 lines)
    From: priyanka singh <priyanka.priyankasingh@GMAIL.COM>

  165. Re: How to store t-stat in sas dataset form in proc autoreg ? (33 lines)
    From: Murphy Choy <goladin@GMAIL.COM>

  166. SAS 9.2. Windows 7 x64 Ultimate. Setup.exe not initialising (44 lines)
    From: Winston Groenewald <winston.groenewald@GMAIL.COM>

  167. tagset.RTF controlling page breaks (22 lines)
    From: Paul <paulsrowland@YAHOO.COM>

  168. Re: SAS 9.2. Windows 7 x64 Ultimate. Setup.exe not initialising (67 lines)
    From: Winston Groenewald <winston.groenewald@GMAIL.COM>

  169. Re: Is there a better way to calculate fiscal year? (115 lines)
    From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

  170. Re: NLMIXED vs GLIMMIX (72 lines)
    From: oslo <hokut1@YAHOO.COM>

  171. Re: Is there a better way to calculate fiscal year? (157 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  172. Log Likelihood for Hurdle Poisson (Additional Truncation) (38 lines)
    From: Ryan Black <ryan.andrew.black@GMAIL.COM>

  173. Making a range of local variables. (16 lines)
    From: Sterling Paramore <gnilrets@GMAIL.COM>

  174. Re: Making a range of local variables. (32 lines)
    From: Wensui Liu <liuwensui@GMAIL.COM>

  175. How to populate newly created variables with user inputs with PROC PMENU? Options I used the following codes to (83 lines)
    From: Chi Shu <chichi_cn@LIVE.COM>

  176. Re: Making a range of local variables. (65 lines)
    From: toby dunn <tobydunn@HOTMAIL.COM>

  177. Re: Making a range of local variables. (51 lines)
    From: shyamprasad samisetti <shyam.cbz@GMAIL.COM>

  178. Re: Making a range of local variables. (55 lines)
    From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

  179. Re: Log Likelihood for Hurdle Poisson (Additional Truncation) (112 lines)
    From: Dale McLerran <stringplayer_2@YAHOO.COM>

  180. PROC Report Help (123 lines)
    From: saslearn chicago <sasswamy@GMAIL.COM>

  181. Re: PROC Report Help (139 lines)
    From: Yu Zhang <zhangyu05@GMAIL.COM>

  182. Re: Making a range of local variables. (52 lines)
    From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

  183. Re: Log Likelihood for Hurdle Poisson (Additional Truncation) (157 lines)
    From: Ryan Black <ryan.andrew.black@GMAIL.COM>

  184. The Virginia SAS User's Group (VASUG) meets on June 25 (45 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  185. Re: How to store t-stat in sas dataset form in proc autoreg ? (38 lines)
    From: priyanka singh <priyanka.priyankasingh@GMAIL.COM>

  186. OT: Thursday Theory (38 lines)
    From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

  187. Re: Producing 4D scatter plot with Proc G3D (79 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  188. Proc Export to Microsoft Access Database: Poor Performance (41 lines)
    From: Kevin Myers <kmyers1@CLEARWIRE.NET>

  189. Re: Proc Export to Microsoft Access Database: Poor Performance (52 lines)
    From: Kevin Myers <kmyers1@CLEARWIRE.NET>

  190. Re: Proc Export to Microsoft Access Database: Poor Performance (55 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  191. Re: Proc Export to Microsoft Access Database: Poor Performance (81 lines)
    From: Kevin Myers <kmyers1@CLEARWIRE.NET>

  192. Re: Proc Export to Microsoft Access Database: Poor Performance (90 lines)
    From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

  193. Re: Proc Export to Microsoft Access Database: Poor Performance (121 lines)
    From: Kevin Myers <kmyers1@CLEARWIRE.NET>

  194. Re: Proc Export to Microsoft Access Database: Poor Performance (145 lines)
    From: Philip Rack <PhilRack@MINEQUEST.COM>

  195. Re: Proc Export to Microsoft Access Database: Poor Performance (171 lines)
    From: Kevin Myers <kmyers1@CLEARWIRE.NET>

  196. Re: Proc Export to Microsoft Access Database: Poor Performance (196 lines)
    From: Philip Rack <PhilRack@MINEQUEST.COM>

  197. Re: Proc Export to Microsoft Access Database: Poor Performance (217 lines)
    From: Nat Wooding <nathani@VERIZON.NET>

  198. Re: Proc Export to Microsoft Access Database: Poor Performance (250 lines)
    From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>

  199. Re: Producing 4D scatter plot with Proc G3D (222 lines)
    From: Hoyle, Larry <larryhoyle@KU.EDU>

  200. Summing Variables (35 lines)
    From: Randy <randistan69@HOTMAIL.COM>

  201. Job Posting, Statistical Team Leader, Vermont Oxford Network (137 lines)
    From: Joe Carpenter <Joe@VTOXFORD.ORG>

  202. Re: Summing Variables (82 lines)
    From: Ya Huang <ya.huang@AMYLIN.COM>

  203. Question about SAS macro variables and PROC PMENU (73 lines)
    From: Chi Shu <chichi_cn@LIVE.COM>

  204. Re: PROC Report Help (161 lines)
    From: saslearn chicago <sasswamy@GMAIL.COM>

  205. Re: Question about SAS macro variables and PROC PMENU (85 lines)
    From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

  206. Re: PROC Report Help (184 lines)
    From: Yu Zhang <zhangyu05@GMAIL.COM>

  207. Re: Question about SAS macro variables and PROC PMENU (127 lines)
    From: Chi Shu <chichi_cn@LIVE.COM>

  208. Newbie Loop Question (41 lines)
    From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

  209. Categorical predictor and dependent variable(s) (21 lines)
    From: Steve Woods <woods.steve@GMAIL.COM>

  210. Re: PROC Report Help (319 lines)
    From: saslearn chicago <sasswamy@GMAIL.COM>

  211. Re: Newbie Loop Question (109 lines)
    From: My Name <lewjord@UGA.EDU>

  212. Re: I want to move SQL connection strings out of my SAS code (66 lines)
    From: Viel, Kevin <kviel@SJHA.ORG>

  213. Re: PROC Report Help (387 lines)
    From: saslearn chicago <sasswamy@GMAIL.COM>

  214. EFFECT SIZE FOR MIXED MODELS XXXX (16 lines)
    From: Dan Abner <dan.abner99@GMAIL.COM>

  215. ODS Graphics Output, ImageName (30 lines)
    From: Ryan Krause <ryan.krause@GMAIL.COM>

  216. Re: PROC Report Help (50 lines)
    From: Tom Abernathy <tom.abernathy@GMAIL.COM>

Back to the main SAS-L page