Ali Zanaty <zanaty2005@YAHOO.COM>teaching SAS (18 lines) Re: teaching SAS (78 lines) Allen Ziegenfus <aziegenfus@GMAIL.COM>Sas File Locking (63 lines) Re: modulen: where does SAS look? (75 lines) Amy Krueger <amyk4422@GMAIL.COM>relative risk with proc freq multiple variables (34 lines) Arthur Tabachneck <art297@ROGERS.COM>Re: CI and SE bars (43 lines) Re: CI and SE bars (90 lines) Re: Calculating Readmissions (26 lines) Re: Calculating Readmissions (71 lines) Re: Calculating Readmissions (206 lines) Re: Calculating Readmissions (61 lines) Can one recover a deleted log? (15 lines) Re: Can one recover a deleted log? (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (73 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (24 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (98 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (48 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Least and most helpful SAS error message (37 lines) Re: Macro Reading Filename (91 lines) Re: Maximum Size for Character Variables? (98 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (101 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (160 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (69 lines) Re: PROC EXPLODE and semicolons (83 lines) Re: Proc SQL BETWEEN statement is less efficient? (41 lines) Re: Proc SQL BETWEEN statement is less efficient? (61 lines) Re: SAS on iPad? (40 lines) Re: Sign after the numbers (67 lines) Re: Sign after the numbers (117 lines) Re: The d in w.d informat (113 lines) Re: blanks in html output (50 lines) Re: finding gaps given date ranges and covered date ranges (121 lines) Re: partitioning a variable (65 lines) Bartells, Paul <Paul.Bartells@TARGETBASE.COM>Re: PROC FORMAT with dates (102 lines) Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>CI and SE bars (23 lines) Re: CI and SE bars (65 lines) Re: CI and SE bars (76 lines) Re: CI and SE bars (39 lines) Re: CI and SE bars (48 lines) subject terms in the repeated measures mixed model, split plot with RCBD (78 lines) Braun, Joseph M. <joebraun@PURDUE.EDU>Recovering a deleted log (22 lines) Brian Trautman <btrautman84@GMAIL.COM>Macro Reading Filename (39 lines) Re: Macro Reading Filename (71 lines) Re: Macro Reading Filename (116 lines) Re: Macro Reading Filename (138 lines) Carol Bristow <Carol.Bristow@DPRA.COM>Re: Proc sql pass through, meta data, proc contents? (124 lines) Carol Olson <Carol.Olson@MEREDITH.COM>Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27) (14 lines) Chang Chung <chang_y_chung@HOTMAIL.COM>Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines) Sign after the numbers (27 lines) Re: The d in w.d informat (35 lines) finding gaps given date ranges and covered date ranges (33 lines) Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Allen Ziegenfus <aziegenfus@GMAIL.COM>Sas File Locking (63 lines) Re: modulen: where does SAS look? (75 lines) Amy Krueger <amyk4422@GMAIL.COM>relative risk with proc freq multiple variables (34 lines) Arthur Tabachneck <art297@ROGERS.COM>Re: CI and SE bars (43 lines) Re: CI and SE bars (90 lines) Re: Calculating Readmissions (26 lines) Re: Calculating Readmissions (71 lines) Re: Calculating Readmissions (206 lines) Re: Calculating Readmissions (61 lines) Can one recover a deleted log? (15 lines) Re: Can one recover a deleted log? (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (73 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (24 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (98 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (48 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Least and most helpful SAS error message (37 lines) Re: Macro Reading Filename (91 lines) Re: Maximum Size for Character Variables? (98 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (101 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (160 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (69 lines) Re: PROC EXPLODE and semicolons (83 lines) Re: Proc SQL BETWEEN statement is less efficient? (41 lines) Re: Proc SQL BETWEEN statement is less efficient? (61 lines) Re: SAS on iPad? (40 lines) Re: Sign after the numbers (67 lines) Re: Sign after the numbers (117 lines) Re: The d in w.d informat (113 lines) Re: blanks in html output (50 lines) Re: finding gaps given date ranges and covered date ranges (121 lines) Re: partitioning a variable (65 lines) Bartells, Paul <Paul.Bartells@TARGETBASE.COM>Re: PROC FORMAT with dates (102 lines) Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>CI and SE bars (23 lines) Re: CI and SE bars (65 lines) Re: CI and SE bars (76 lines) Re: CI and SE bars (39 lines) Re: CI and SE bars (48 lines) subject terms in the repeated measures mixed model, split plot with RCBD (78 lines) Braun, Joseph M. <joebraun@PURDUE.EDU>Recovering a deleted log (22 lines) Brian Trautman <btrautman84@GMAIL.COM>Macro Reading Filename (39 lines) Re: Macro Reading Filename (71 lines) Re: Macro Reading Filename (116 lines) Re: Macro Reading Filename (138 lines) Carol Bristow <Carol.Bristow@DPRA.COM>Re: Proc sql pass through, meta data, proc contents? (124 lines) Carol Olson <Carol.Olson@MEREDITH.COM>Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27) (14 lines) Chang Chung <chang_y_chung@HOTMAIL.COM>Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines) Sign after the numbers (27 lines) Re: The d in w.d informat (35 lines) finding gaps given date ranges and covered date ranges (33 lines) Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Amy Krueger <amyk4422@GMAIL.COM>relative risk with proc freq multiple variables (34 lines) Arthur Tabachneck <art297@ROGERS.COM>Re: CI and SE bars (43 lines) Re: CI and SE bars (90 lines) Re: Calculating Readmissions (26 lines) Re: Calculating Readmissions (71 lines) Re: Calculating Readmissions (206 lines) Re: Calculating Readmissions (61 lines) Can one recover a deleted log? (15 lines) Re: Can one recover a deleted log? (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (73 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (24 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (98 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (48 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Least and most helpful SAS error message (37 lines) Re: Macro Reading Filename (91 lines) Re: Maximum Size for Character Variables? (98 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (101 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (160 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (69 lines) Re: PROC EXPLODE and semicolons (83 lines) Re: Proc SQL BETWEEN statement is less efficient? (41 lines) Re: Proc SQL BETWEEN statement is less efficient? (61 lines) Re: SAS on iPad? (40 lines) Re: Sign after the numbers (67 lines) Re: Sign after the numbers (117 lines) Re: The d in w.d informat (113 lines) Re: blanks in html output (50 lines) Re: finding gaps given date ranges and covered date ranges (121 lines) Re: partitioning a variable (65 lines) Bartells, Paul <Paul.Bartells@TARGETBASE.COM>Re: PROC FORMAT with dates (102 lines) Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>CI and SE bars (23 lines) Re: CI and SE bars (65 lines) Re: CI and SE bars (76 lines) Re: CI and SE bars (39 lines) Re: CI and SE bars (48 lines) subject terms in the repeated measures mixed model, split plot with RCBD (78 lines) Braun, Joseph M. <joebraun@PURDUE.EDU>Recovering a deleted log (22 lines) Brian Trautman <btrautman84@GMAIL.COM>Macro Reading Filename (39 lines) Re: Macro Reading Filename (71 lines) Re: Macro Reading Filename (116 lines) Re: Macro Reading Filename (138 lines) Carol Bristow <Carol.Bristow@DPRA.COM>Re: Proc sql pass through, meta data, proc contents? (124 lines) Carol Olson <Carol.Olson@MEREDITH.COM>Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27) (14 lines) Chang Chung <chang_y_chung@HOTMAIL.COM>Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines) Sign after the numbers (27 lines) Re: The d in w.d informat (35 lines) finding gaps given date ranges and covered date ranges (33 lines) Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Arthur Tabachneck <art297@ROGERS.COM>Re: CI and SE bars (43 lines) Re: CI and SE bars (90 lines) Re: Calculating Readmissions (26 lines) Re: Calculating Readmissions (71 lines) Re: Calculating Readmissions (206 lines) Re: Calculating Readmissions (61 lines) Can one recover a deleted log? (15 lines) Re: Can one recover a deleted log? (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (73 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (24 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (98 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (48 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Least and most helpful SAS error message (37 lines) Re: Macro Reading Filename (91 lines) Re: Maximum Size for Character Variables? (98 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (101 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (160 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (69 lines) Re: PROC EXPLODE and semicolons (83 lines) Re: Proc SQL BETWEEN statement is less efficient? (41 lines) Re: Proc SQL BETWEEN statement is less efficient? (61 lines) Re: SAS on iPad? (40 lines) Re: Sign after the numbers (67 lines) Re: Sign after the numbers (117 lines) Re: The d in w.d informat (113 lines) Re: blanks in html output (50 lines) Re: finding gaps given date ranges and covered date ranges (121 lines) Re: partitioning a variable (65 lines) Bartells, Paul <Paul.Bartells@TARGETBASE.COM>Re: PROC FORMAT with dates (102 lines) Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>CI and SE bars (23 lines) Re: CI and SE bars (65 lines) Re: CI and SE bars (76 lines) Re: CI and SE bars (39 lines) Re: CI and SE bars (48 lines) subject terms in the repeated measures mixed model, split plot with RCBD (78 lines) Braun, Joseph M. <joebraun@PURDUE.EDU>Recovering a deleted log (22 lines) Brian Trautman <btrautman84@GMAIL.COM>Macro Reading Filename (39 lines) Re: Macro Reading Filename (71 lines) Re: Macro Reading Filename (116 lines) Re: Macro Reading Filename (138 lines) Carol Bristow <Carol.Bristow@DPRA.COM>Re: Proc sql pass through, meta data, proc contents? (124 lines) Carol Olson <Carol.Olson@MEREDITH.COM>Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27) (14 lines) Chang Chung <chang_y_chung@HOTMAIL.COM>Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines) Sign after the numbers (27 lines) Re: The d in w.d informat (35 lines) finding gaps given date ranges and covered date ranges (33 lines) Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Bartells, Paul <Paul.Bartells@TARGETBASE.COM>Re: PROC FORMAT with dates (102 lines) Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>CI and SE bars (23 lines) Re: CI and SE bars (65 lines) Re: CI and SE bars (76 lines) Re: CI and SE bars (39 lines) Re: CI and SE bars (48 lines) subject terms in the repeated measures mixed model, split plot with RCBD (78 lines) Braun, Joseph M. <joebraun@PURDUE.EDU>Recovering a deleted log (22 lines) Brian Trautman <btrautman84@GMAIL.COM>Macro Reading Filename (39 lines) Re: Macro Reading Filename (71 lines) Re: Macro Reading Filename (116 lines) Re: Macro Reading Filename (138 lines) Carol Bristow <Carol.Bristow@DPRA.COM>Re: Proc sql pass through, meta data, proc contents? (124 lines) Carol Olson <Carol.Olson@MEREDITH.COM>Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27) (14 lines) Chang Chung <chang_y_chung@HOTMAIL.COM>Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines) Sign after the numbers (27 lines) Re: The d in w.d informat (35 lines) finding gaps given date ranges and covered date ranges (33 lines) Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>CI and SE bars (23 lines) Re: CI and SE bars (65 lines) Re: CI and SE bars (76 lines) Re: CI and SE bars (39 lines) Re: CI and SE bars (48 lines) subject terms in the repeated measures mixed model, split plot with RCBD (78 lines) Braun, Joseph M. <joebraun@PURDUE.EDU>Recovering a deleted log (22 lines) Brian Trautman <btrautman84@GMAIL.COM>Macro Reading Filename (39 lines) Re: Macro Reading Filename (71 lines) Re: Macro Reading Filename (116 lines) Re: Macro Reading Filename (138 lines) Carol Bristow <Carol.Bristow@DPRA.COM>Re: Proc sql pass through, meta data, proc contents? (124 lines) Carol Olson <Carol.Olson@MEREDITH.COM>Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27) (14 lines) Chang Chung <chang_y_chung@HOTMAIL.COM>Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines) Sign after the numbers (27 lines) Re: The d in w.d informat (35 lines) finding gaps given date ranges and covered date ranges (33 lines) Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Braun, Joseph M. <joebraun@PURDUE.EDU>Recovering a deleted log (22 lines) Brian Trautman <btrautman84@GMAIL.COM>Macro Reading Filename (39 lines) Re: Macro Reading Filename (71 lines) Re: Macro Reading Filename (116 lines) Re: Macro Reading Filename (138 lines) Carol Bristow <Carol.Bristow@DPRA.COM>Re: Proc sql pass through, meta data, proc contents? (124 lines) Carol Olson <Carol.Olson@MEREDITH.COM>Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27) (14 lines) Chang Chung <chang_y_chung@HOTMAIL.COM>Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines) Sign after the numbers (27 lines) Re: The d in w.d informat (35 lines) finding gaps given date ranges and covered date ranges (33 lines) Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Brian Trautman <btrautman84@GMAIL.COM>Macro Reading Filename (39 lines) Re: Macro Reading Filename (71 lines) Re: Macro Reading Filename (116 lines) Re: Macro Reading Filename (138 lines) Carol Bristow <Carol.Bristow@DPRA.COM>Re: Proc sql pass through, meta data, proc contents? (124 lines) Carol Olson <Carol.Olson@MEREDITH.COM>Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27) (14 lines) Chang Chung <chang_y_chung@HOTMAIL.COM>Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines) Sign after the numbers (27 lines) Re: The d in w.d informat (35 lines) finding gaps given date ranges and covered date ranges (33 lines) Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Carol Bristow <Carol.Bristow@DPRA.COM>Re: Proc sql pass through, meta data, proc contents? (124 lines) Carol Olson <Carol.Olson@MEREDITH.COM>Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27) (14 lines) Chang Chung <chang_y_chung@HOTMAIL.COM>Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines) Sign after the numbers (27 lines) Re: The d in w.d informat (35 lines) finding gaps given date ranges and covered date ranges (33 lines) Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Carol Olson <Carol.Olson@MEREDITH.COM>Automatic reply: SAS-L Digest - 7 Jan 2011 - Special issue (#2011-27) (14 lines) Chang Chung <chang_y_chung@HOTMAIL.COM>Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines) Sign after the numbers (27 lines) Re: The d in w.d informat (35 lines) finding gaps given date ranges and covered date ranges (33 lines) Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Chang Chung <chang_y_chung@HOTMAIL.COM>Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (35 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (165 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (13 lines) Sign after the numbers (27 lines) Re: The d in w.d informat (35 lines) finding gaps given date ranges and covered date ranges (33 lines) Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Chen, Jian (CDC/ONDIEH/NCCDPHP) (CTR) <ozz6@CDC.GOV>Re: teaching SAS (68 lines) Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Chris Brooks <Chris.Brooks@ONS.GOV.UK>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (226 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (290 lines) Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Craig Johnson <cjohns38@GMAIL.COM>SQL Full Join Problem (106 lines) DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
DUELL, BOB (ATTCINW) <BD9439@ATT.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (86 lines) Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (44 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (412 lines) Re: Proc SQL BETWEEN statement is less efficient? (55 lines) Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Dale McLerran <stringplayer_2@YAHOO.COM>Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (60 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (184 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (89 lines) Re: proc mixed 4-levels (59 lines) Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Data _null_; <iebupdte@GMAIL.COM>Re: PROC EXPLODE and semicolons (21 lines) Re: Recovering a deleted log (33 lines) Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Duck-Hye Yang <dyang@CHAPINHALL.ORG>Re: Unix SAS (128 lines) Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Eric Hoogenboom <erichoogenboom@YAHOO.COM>Re: IBNR / Chain Ladder (15 lines) Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>Re: Can one recover a deleted log? (36 lines) Re: Least and most helpful SAS error message (41 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (407 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (498 lines) Re: Prevent procedure output from beginning on a new page (46 lines) SAS on iPad? (22 lines) SAS v9.3 ship date (35 lines) Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (37 lines) Re: Is it sorted? Are there performance benefits? (75 lines) Re: Is it sorted? Are there performance benefits? (230 lines) Re: Least and most helpful SAS error message (134 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (111 lines) Re: Sign after the numbers (80 lines) Re: Sign after the numbers (107 lines) Re: the compute block in proc report (77 lines) Re: the compute block in proc report (120 lines) Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>Re: xlm to SAS dataset (46 lines) Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Gilsen, Bruce F. <bruce.gilsen@FRB.GOV>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (98 lines) HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
HIMS <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (54 lines) Re: Calculating Readmissions (98 lines) Re: Calculating Readmissions (221 lines) Re: Calculating Readmissions (81 lines) Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Huang, Ya <Ya.Huang@AMYLIN.COM>Re: Proc sql pass through, meta data, proc contents? (32 lines) Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Jack Clark <jclark@HILLTOP.UMBC.EDU>Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (363 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (464 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (245 lines) Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Jack Hamilton <jfh@STANFORDALUMNI.ORG>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (121 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (154 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (303 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (80 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (135 lines) Re: Proc SQL BETWEEN statement is less efficient? (50 lines) Re: SAS on iPad? (32 lines) Re: SAS on iPad? (50 lines) Re: partitioning a variable (43 lines) James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
James Algina <algina@UFL.EDU>RTF Output (36 lines) James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
James Oliver <james.oliver@STATE.OR.US>modulen: where does SAS look? (59 lines) Re: modulen: where does SAS look? (15 lines) Re: modulen: where does SAS look? (39 lines) Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Jamil M Ibrahim <jibrahim@UMC.EDU>Your webmail quota has exceeded the set quota which is 20GB. (28 lines) Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>proc mixed 4-levels (50 lines) Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Jeremy Miles <jeremy.miles@GMAIL.COM>Re: SAS on iPad? (22 lines) Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Jerry <i89rt5@GMAIL.COM>Proc SQL BETWEEN statement is less efficient? (27 lines) Re: Proc SQL BETWEEN statement is less efficient? (73 lines) Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Joe Matise <snoopy369@GMAIL.COM>Re: Can one recover a deleted log? (30 lines) Re: How does SAS Handle This? (48 lines) Re: How does SAS Handle This? (178 lines) Re: How to manipulate data (35 lines) Re: How to manipulate data (72 lines) Re: Is it sorted? Are there performance benefits? (138 lines) Re: Is it sorted? Are there performance benefits? (202 lines) Re: Macro Reading Filename (57 lines) Re: Macro Reading Filename (131 lines) Re: ODS PDF (30 lines) Re: ODS PDF (57 lines) Re: PROC FORMAT with dates (75 lines) Re: Proc sql pass through, meta data, proc contents? (45 lines) Re: The d in w.d informat (126 lines) Re: help with matching without replacement (49 lines) Re: the compute block in proc report (67 lines) Re: the compute block in proc report (119 lines) Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Joe Whitehurst <joewhitehurst@GMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (116 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (50 lines) John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
John Birken <zbq5@CDC.GOV>Re: ODS HTML Question (67 lines) John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
John Mike <sasslick@GMAIL.COM>ODS PDF (14 lines) Re: ODS PDF (42 lines) SAS Unix (15 lines) Re: SAS Unix (69 lines) Unix SAS (15 lines) Re: Unix SAS (49 lines) Re: Unix SAS (103 lines) Re: Unix SAS (56 lines) Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Jonas Bilenas <jonas.bilenas@CHASE.COM>Re: Unix SAS (37 lines) Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Karen L <hl2493@YAHOO.COM>how to show variables with its full infomation in viewtable (16 lines) Re: how to show variables with its full infomation in viewtable (22 lines) partitioning a variable (18 lines) Re: partitioning a variable (30 lines) Re: partitioning a variable (34 lines) Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (59 lines) Re: How does SAS Handle This? (160 lines) Re: Is it sorted? Are there performance benefits? (176 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (146 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (190 lines) Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Kirby, Ted <ted.kirby@LEWIN.COM>Re: Can one recover a deleted log? (65 lines) FW: Re: PROC EXPLODE and semicolons (43 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines) Maximum Size for Character Variables? (96 lines) Multiple Semicolons (was PROC EXPLODE and semicolons) (87 lines) NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (450 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (465 lines) Re: NRows was (RE: Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma) (540 lines) PROC EXPLODE and semicolons (64 lines) Re: the compute block in proc report (113 lines) Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Ksharp <xiakeshan@YAHOO.COM.CN>Re: blanks in html output (20 lines) Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>PROC GCHART: Explicitly control the ordering of group variables (124 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (204 lines) Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Michael Raithel <michaelraithel@WESTAT.COM>Re: CI and SE bars (56 lines) Re: Least and most helpful SAS error message (45 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (39 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (53 lines) Re: Proc SQL BETWEEN statement is less efficient? (47 lines) Re: Proc SQL BETWEEN statement is less efficient? (75 lines) Re: teaching SAS (53 lines) Re: teaching SAS (59 lines) Re: teaching SAS (47 lines) Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Mike Zdeb <msz03@ALBANY.EDU>Re: Is it sorted? Are there performance benefits? (123 lines) Re: Is it sorted? Are there performance benefits? (150 lines) Re: The d in w.d informat (185 lines) Re: teaching SAS (95 lines) Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (16 lines) Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Murphy Choy <goladin@GMAIL.COM>Re: teaching SAS (109 lines) Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Nat Wooding <nathani@VERIZON.NET>Re: CI and SE bars (62 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (125 lines) Re: Least and most helpful SAS error message (33 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (269 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (49 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (93 lines) Re: Sign after the numbers (58 lines) Re: Unix SAS (48 lines) Re: partitioning a variable (91 lines) Re: teaching SAS (45 lines) Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>Re: Is it sorted? Are there performance benefits? (111 lines) Re: Is it sorted? Are there performance benefits? (307 lines) Re: Is it sorted? Are there performance benefits? (338 lines) Re: Love With SAS - My Vote for my favorite SAS Programming Language "Feature" (73 lines) Re: partitioning a variable (101 lines) Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Paul Bartells <paul.bartells@TARGETBASE.COM>PROC FORMAT with dates (62 lines) Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Paul Hamilton <pdhamilton1@COMCAST.NET>Re: RTF Output (64 lines) Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Peter <phlarsen@YAHOO.COM>Re: Misc. SAS Gplot/Greplay Questions (266 lines) Re: Misc. SAS Gplot/Greplay Questions (408 lines) Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Peter Flom <peterflomconsulting@MINDSPRING.COM>Re: CI and SE bars (40 lines) Re: CI and SE bars (29 lines) Re: CI and SE bars (22 lines) Re: CI and SE bars (35 lines) Re: CI and SE bars (26 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (19 lines) Least and most helpful SAS error message (20 lines) Re: Logistic Regression Intercept Pr>Chisq (48 lines) Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Peter the SAS Hack <phlarsen@YAHOO.COM>Misc. SAS Gplot/Greplay Questions (201 lines) Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Philip Rack <PhilRack@MINEQUEST.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (203 lines) Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Quentin McMullen <qmcmullen.sas@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (48 lines) Re: Prevent procedure output from beginning on a new page (39 lines) Re: Prevent procedure output from beginning on a new page (37 lines) Re: SAS on iPad? (58 lines) Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Reeza K <fkhurshed@HOTMAIL.COM>Re: Sas File Locking (57 lines) Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Robin R High <rhigh@UNMC.EDU>Re: Least and most helpful SAS error message (96 lines) Re: Logistic Regression Intercept Pr>Chisq (78 lines) Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Schwarz, Barry A <barry.a.schwarz@BOEING.COM>Re: partitioning a variable (42 lines) Re: partitioning a variable (38 lines) Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Scott Bass <sas_l_739@YAHOO.COM.AU>Prevent procedure output from beginning on a new page (85 lines) Re: Prevent procedure output from beginning on a new page (18 lines) Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Shelley Perritt <hims.sperritt@SYMPATICO.CA>Re: Calculating Readmissions (129 lines) Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Stehle, James <James.Stehle@BEA.GOV>The d in w.d informat (98 lines) Re: The d in w.d informat (146 lines) Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Stephen Ellwood <stephen.ellwood@ZOO.OX.AC.UK>unsubscribe sas-l (1040 lines) Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Sterling Paramore <gnilrets@GMAIL.COM>Is it sorted? Are there performance benefits? (44 lines) Re: Is it sorted? Are there performance benefits? (122 lines) Re: Is it sorted? Are there performance benefits? (151 lines) Re: Is it sorted? Are there performance benefits? (190 lines) Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Susan Durham <sdurham@BIOLOGY.USU.EDU>Re: CI and SE bars (89 lines) Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (124 lines) Re: Multiple Semicolons (was PROC EXPLODE and semicolons) (302 lines) Re: Proc sql pass through, meta data, proc contents? (54 lines) Re: RTF Output (46 lines) Re: Sas File Locking (50 lines) Re: Sas File Locking (58 lines) Re: Sas File Locking (68 lines) Re: Unix SAS (44 lines) Re: xlm to SAS dataset (23 lines) Re: xlm to SAS dataset (64 lines) Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Søren Lassen <s.lassen@POST.TELE.DK>Re: How does SAS Handle This? (95 lines) Re: Macro Reading Filename (92 lines) Re: Proc sql pass through, meta data, proc contents? (67 lines) Re: modulen: where does SAS look? (96 lines) T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
T J <tj_noreply@YAHOO.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (36 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (30 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (67 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (103 lines) Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (123 lines) Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Tanmoy Mukherjee <tkmcornell@YAHOO.COM>Logistic Regression Intercept Pr>Chisq (37 lines) Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Terjeson, Mark <Mterjeson@RUSSELL.COM>Re: SAS Unix (61 lines) Re: SAS Unix (119 lines) Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>xlm to SAS dataset (17 lines) Re: xlm to SAS dataset (54 lines) Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Tom Abernathy <tom.abernathy@GMAIL.COM>Re: Sas File Locking (33 lines) Re: Unix SAS (91 lines) Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Tom Robinson <barefootguru@GMAIL.COM>Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (21 lines) Re: the compute block in proc report (47 lines) Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Tracy Li <lisiqi77@YAHOO.COM>help with matching without replacement (33 lines) Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Viel, Kevin <kviel@SJHA.ORG>HTML tags in ODS HTML files (46 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (88 lines) Re: help with matching without replacement (77 lines) Re: teaching SAS (78 lines) Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Wensui Liu <liuwensui@GMAIL.COM>markov transition model with binary response (22 lines) Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Ya Huang <ya.huang@AMYLIN.COM>Re: Misc. SAS Gplot/Greplay Questions (234 lines) Re: Misc. SAS Gplot/Greplay Questions (303 lines) Re: Misc. SAS Gplot/Greplay Questions (364 lines) Re: Misc. SAS Gplot/Greplay Questions (392 lines) Re: ODS PDF (68 lines) Re: PROC GCHART: Explicitly control the ordering of group variables (150 lines) Proc sql pass through, meta data, proc contents? (25 lines) Re: blanks in html output (73 lines) Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
Yu Zhang <zhangyu05@GMAIL.COM>Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (286 lines) bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
bbser 2009 <bbser2009@GMAIL.COM>Re: Sign after the numbers (99 lines) Re: Sign after the numbers (128 lines) blanks in html output (29 lines) Re: help with matching without replacement (63 lines) Re: partitioning a variable (49 lines) the compute block in proc report (33 lines) df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
df ss <tggsun@YAHOO.COM>gplot question color of reference line (22 lines) toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
toby dunn <tobydunn@HOTMAIL.COM>Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (47 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (403 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (539 lines) Re: Macro Quoting Issue (I think) - Problem with CALL EXECUTE parameter values with Apostrophe, Comma (84 lines) Re: Sign after the numbers (63 lines) Re: Unix SAS (41 lines) Re: Unix SAS (85 lines) Re: partitioning a variable (56 lines) vivian v <v.vivian3@GMAIL.COM>
vivian v <v.vivian3@GMAIL.COM>
![[Separator]](/archives/images/ls1-sep.gif){kind=small}
