%hashmerge macroRe: %hashmerge macro (162 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: %hashmerge macro (189 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: %hashmerge macro (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: %hashmerge macro (167 lines) From: Gregg Snell <sas@DATASAVANTCONSULTING.COM> Re: %hashmerge macro (153 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: %hashmerge macro (104 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> %hashmerge macro (87 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> =?utf-8?B?UmU6IHByeCBtYXRjaGluZyAiYWxsIHRoZSBjaGFyYWN0ZXJzIGFyZSB0aGUgc2FtZSI=?==?utf-8?B?UmU6IHByeCBtYXRjaGluZyAiYWxsIHRoZSBjaGFyYWN0ZXJzIGFyZSB0aGUgc2FtZSI=?= (26 lines) From: =?utf-8?B?dG9ieWR1bm5AaG90bWFpbC5jb20=?= <tobydunn@HOTMAIL.COM> A question about opening data in sas/iml studioRe: A question about opening data in sas/iml studio (23 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> A question about opening data in sas/iml studio (38 lines) From: Moo Hwan Kim <kmhlmj2@HOTMAIL.COM> Aaargh fomat/informat :-(Re: Aaargh fomat/informat :-( (73 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Aaargh fomat/informat :-( (70 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Aaargh fomat/informat :-( (46 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Aaargh fomat/informat :-( (46 lines) From: Jonas Bilenas <jonas.bilenas@CHASE.COM> Re: Aaargh fomat/informat :-( (41 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Aaargh fomat/informat :-( (25 lines) From: Laughing Beggar <laughing_beggar@HOTMAIL.COM> Automatic reply: SAS-L Digest - 17 Jul 2010 to 18 Jul 2010 - Special issue (#2010-826)Automatic reply: SAS-L Digest - 17 Jul 2010 to 18 Jul 2010 - Special issue (#2010-826) (15 lines) From: Robert Ligtenberg <Robert.Ligtenberg@SAS.COM> Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (208 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (180 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (355 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (216 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (44 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (10 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (226 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (312 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (224 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (255 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (235 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (180 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (149 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (197 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (215 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (195 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (157 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (127 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (79 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (15 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (61 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (212 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (141 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> CEDA - Native Data SetRe: CEDA - Native Data Set (72 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: CEDA - Native Data Set (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: CEDA - Native Data Set (73 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: CEDA - Native Data Set (53 lines) From: Mary <mlhoward@AVALON.NET> CEDA - Native Data Set (27 lines) From: SAS Swamy <sasswamy@GMAIL.COM> COUNTREG questionsRe: COUNTREG questions (40 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: COUNTREG questions (127 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (98 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (83 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (67 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> COUNTREG questions (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Changing type and length of multiple variablesRe: Changing type and length of multiple variables (132 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Changing type and length of multiple variables (92 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Changing type and length of multiple variables (32 lines) From: William Krause <wkrause2003@YAHOO.COM> Character Date Conversion in PROC SQLRe: Character Date Conversion in PROC SQL (65 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Character Date Conversion in PROC SQL (44 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Character Date Conversion in PROC SQL (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Character Date Conversion in PROC SQL (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
=?utf-8?B?UmU6IHByeCBtYXRjaGluZyAiYWxsIHRoZSBjaGFyYWN0ZXJzIGFyZSB0aGUgc2FtZSI=?==?utf-8?B?UmU6IHByeCBtYXRjaGluZyAiYWxsIHRoZSBjaGFyYWN0ZXJzIGFyZSB0aGUgc2FtZSI=?= (26 lines) From: =?utf-8?B?dG9ieWR1bm5AaG90bWFpbC5jb20=?= <tobydunn@HOTMAIL.COM> A question about opening data in sas/iml studioRe: A question about opening data in sas/iml studio (23 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> A question about opening data in sas/iml studio (38 lines) From: Moo Hwan Kim <kmhlmj2@HOTMAIL.COM> Aaargh fomat/informat :-(Re: Aaargh fomat/informat :-( (73 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Aaargh fomat/informat :-( (70 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Aaargh fomat/informat :-( (46 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Aaargh fomat/informat :-( (46 lines) From: Jonas Bilenas <jonas.bilenas@CHASE.COM> Re: Aaargh fomat/informat :-( (41 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Aaargh fomat/informat :-( (25 lines) From: Laughing Beggar <laughing_beggar@HOTMAIL.COM> Automatic reply: SAS-L Digest - 17 Jul 2010 to 18 Jul 2010 - Special issue (#2010-826)Automatic reply: SAS-L Digest - 17 Jul 2010 to 18 Jul 2010 - Special issue (#2010-826) (15 lines) From: Robert Ligtenberg <Robert.Ligtenberg@SAS.COM> Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (208 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (180 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (355 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (216 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (44 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (10 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (226 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (312 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (224 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (255 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (235 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (180 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (149 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (197 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (215 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (195 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (157 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (127 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (79 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (15 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (61 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (212 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (141 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> CEDA - Native Data SetRe: CEDA - Native Data Set (72 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: CEDA - Native Data Set (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: CEDA - Native Data Set (73 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: CEDA - Native Data Set (53 lines) From: Mary <mlhoward@AVALON.NET> CEDA - Native Data Set (27 lines) From: SAS Swamy <sasswamy@GMAIL.COM> COUNTREG questionsRe: COUNTREG questions (40 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: COUNTREG questions (127 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (98 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (83 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (67 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> COUNTREG questions (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Changing type and length of multiple variablesRe: Changing type and length of multiple variables (132 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Changing type and length of multiple variables (92 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Changing type and length of multiple variables (32 lines) From: William Krause <wkrause2003@YAHOO.COM> Character Date Conversion in PROC SQLRe: Character Date Conversion in PROC SQL (65 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Character Date Conversion in PROC SQL (44 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Character Date Conversion in PROC SQL (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Character Date Conversion in PROC SQL (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
A question about opening data in sas/iml studioRe: A question about opening data in sas/iml studio (23 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> A question about opening data in sas/iml studio (38 lines) From: Moo Hwan Kim <kmhlmj2@HOTMAIL.COM> Aaargh fomat/informat :-(Re: Aaargh fomat/informat :-( (73 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Aaargh fomat/informat :-( (70 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Aaargh fomat/informat :-( (46 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Aaargh fomat/informat :-( (46 lines) From: Jonas Bilenas <jonas.bilenas@CHASE.COM> Re: Aaargh fomat/informat :-( (41 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Aaargh fomat/informat :-( (25 lines) From: Laughing Beggar <laughing_beggar@HOTMAIL.COM> Automatic reply: SAS-L Digest - 17 Jul 2010 to 18 Jul 2010 - Special issue (#2010-826)Automatic reply: SAS-L Digest - 17 Jul 2010 to 18 Jul 2010 - Special issue (#2010-826) (15 lines) From: Robert Ligtenberg <Robert.Ligtenberg@SAS.COM> Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (208 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (180 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (355 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (216 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (44 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (10 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (226 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (312 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (224 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (255 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (235 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (180 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (149 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (197 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (215 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (195 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (157 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (127 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (79 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (15 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (61 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (212 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (141 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> CEDA - Native Data SetRe: CEDA - Native Data Set (72 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: CEDA - Native Data Set (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: CEDA - Native Data Set (73 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: CEDA - Native Data Set (53 lines) From: Mary <mlhoward@AVALON.NET> CEDA - Native Data Set (27 lines) From: SAS Swamy <sasswamy@GMAIL.COM> COUNTREG questionsRe: COUNTREG questions (40 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: COUNTREG questions (127 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (98 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (83 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (67 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> COUNTREG questions (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Changing type and length of multiple variablesRe: Changing type and length of multiple variables (132 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Changing type and length of multiple variables (92 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Changing type and length of multiple variables (32 lines) From: William Krause <wkrause2003@YAHOO.COM> Character Date Conversion in PROC SQLRe: Character Date Conversion in PROC SQL (65 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Character Date Conversion in PROC SQL (44 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Character Date Conversion in PROC SQL (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Character Date Conversion in PROC SQL (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Aaargh fomat/informat :-(Re: Aaargh fomat/informat :-( (73 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Aaargh fomat/informat :-( (70 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Aaargh fomat/informat :-( (46 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Aaargh fomat/informat :-( (46 lines) From: Jonas Bilenas <jonas.bilenas@CHASE.COM> Re: Aaargh fomat/informat :-( (41 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Aaargh fomat/informat :-( (25 lines) From: Laughing Beggar <laughing_beggar@HOTMAIL.COM> Automatic reply: SAS-L Digest - 17 Jul 2010 to 18 Jul 2010 - Special issue (#2010-826)Automatic reply: SAS-L Digest - 17 Jul 2010 to 18 Jul 2010 - Special issue (#2010-826) (15 lines) From: Robert Ligtenberg <Robert.Ligtenberg@SAS.COM> Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (208 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (180 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (355 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (216 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (44 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (10 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (226 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (312 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (224 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (255 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (235 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (180 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (149 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (197 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (215 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (195 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (157 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (127 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (79 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (15 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (61 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (212 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (141 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> CEDA - Native Data SetRe: CEDA - Native Data Set (72 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: CEDA - Native Data Set (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: CEDA - Native Data Set (73 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: CEDA - Native Data Set (53 lines) From: Mary <mlhoward@AVALON.NET> CEDA - Native Data Set (27 lines) From: SAS Swamy <sasswamy@GMAIL.COM> COUNTREG questionsRe: COUNTREG questions (40 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: COUNTREG questions (127 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (98 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (83 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (67 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> COUNTREG questions (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Changing type and length of multiple variablesRe: Changing type and length of multiple variables (132 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Changing type and length of multiple variables (92 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Changing type and length of multiple variables (32 lines) From: William Krause <wkrause2003@YAHOO.COM> Character Date Conversion in PROC SQLRe: Character Date Conversion in PROC SQL (65 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Character Date Conversion in PROC SQL (44 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Character Date Conversion in PROC SQL (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Character Date Conversion in PROC SQL (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Automatic reply: SAS-L Digest - 17 Jul 2010 to 18 Jul 2010 - Special issue (#2010-826)Automatic reply: SAS-L Digest - 17 Jul 2010 to 18 Jul 2010 - Special issue (#2010-826) (15 lines) From: Robert Ligtenberg <Robert.Ligtenberg@SAS.COM> Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (208 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (180 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (355 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (216 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (44 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (10 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (226 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (312 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (224 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (255 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (235 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (180 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (149 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (197 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (215 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (195 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (157 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (127 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (79 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (15 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (61 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (212 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (141 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> CEDA - Native Data SetRe: CEDA - Native Data Set (72 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: CEDA - Native Data Set (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: CEDA - Native Data Set (73 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: CEDA - Native Data Set (53 lines) From: Mary <mlhoward@AVALON.NET> CEDA - Native Data Set (27 lines) From: SAS Swamy <sasswamy@GMAIL.COM> COUNTREG questionsRe: COUNTREG questions (40 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: COUNTREG questions (127 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (98 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (83 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (67 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> COUNTREG questions (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Changing type and length of multiple variablesRe: Changing type and length of multiple variables (132 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Changing type and length of multiple variables (92 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Changing type and length of multiple variables (32 lines) From: William Krause <wkrause2003@YAHOO.COM> Character Date Conversion in PROC SQLRe: Character Date Conversion in PROC SQL (65 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Character Date Conversion in PROC SQL (44 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Character Date Conversion in PROC SQL (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Character Date Conversion in PROC SQL (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (208 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Bona fide DO-loop bug (was: Combining iterative DO and UNTIL condition) (180 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (355 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (216 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (44 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (10 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (226 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (312 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (224 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (255 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (235 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (180 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (149 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (197 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (215 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (195 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (157 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (127 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (79 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (15 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (61 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (212 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (141 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> CEDA - Native Data SetRe: CEDA - Native Data Set (72 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: CEDA - Native Data Set (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: CEDA - Native Data Set (73 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: CEDA - Native Data Set (53 lines) From: Mary <mlhoward@AVALON.NET> CEDA - Native Data Set (27 lines) From: SAS Swamy <sasswamy@GMAIL.COM> COUNTREG questionsRe: COUNTREG questions (40 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: COUNTREG questions (127 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (98 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (83 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (67 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> COUNTREG questions (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Changing type and length of multiple variablesRe: Changing type and length of multiple variables (132 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Changing type and length of multiple variables (92 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Changing type and length of multiple variables (32 lines) From: William Krause <wkrause2003@YAHOO.COM> Character Date Conversion in PROC SQLRe: Character Date Conversion in PROC SQL (65 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Character Date Conversion in PROC SQL (44 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Character Date Conversion in PROC SQL (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Character Date Conversion in PROC SQL (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition)Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (355 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (216 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (44 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (10 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (226 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (312 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (224 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (255 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (235 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (180 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (149 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (197 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (215 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (195 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (157 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (127 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (79 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (15 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (61 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (212 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Bona fide DO-loop bug (was: Re: Combining iterative DO and UNTIL condition) (141 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> CEDA - Native Data SetRe: CEDA - Native Data Set (72 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: CEDA - Native Data Set (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: CEDA - Native Data Set (73 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: CEDA - Native Data Set (53 lines) From: Mary <mlhoward@AVALON.NET> CEDA - Native Data Set (27 lines) From: SAS Swamy <sasswamy@GMAIL.COM> COUNTREG questionsRe: COUNTREG questions (40 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: COUNTREG questions (127 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (98 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (83 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (67 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> COUNTREG questions (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Changing type and length of multiple variablesRe: Changing type and length of multiple variables (132 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Changing type and length of multiple variables (92 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Changing type and length of multiple variables (32 lines) From: William Krause <wkrause2003@YAHOO.COM> Character Date Conversion in PROC SQLRe: Character Date Conversion in PROC SQL (65 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Character Date Conversion in PROC SQL (44 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Character Date Conversion in PROC SQL (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Character Date Conversion in PROC SQL (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
CEDA - Native Data SetRe: CEDA - Native Data Set (72 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: CEDA - Native Data Set (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: CEDA - Native Data Set (73 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: CEDA - Native Data Set (53 lines) From: Mary <mlhoward@AVALON.NET> CEDA - Native Data Set (27 lines) From: SAS Swamy <sasswamy@GMAIL.COM> COUNTREG questionsRe: COUNTREG questions (40 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: COUNTREG questions (127 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (98 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (83 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (67 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> COUNTREG questions (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Changing type and length of multiple variablesRe: Changing type and length of multiple variables (132 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Changing type and length of multiple variables (92 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Changing type and length of multiple variables (32 lines) From: William Krause <wkrause2003@YAHOO.COM> Character Date Conversion in PROC SQLRe: Character Date Conversion in PROC SQL (65 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Character Date Conversion in PROC SQL (44 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Character Date Conversion in PROC SQL (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Character Date Conversion in PROC SQL (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
COUNTREG questionsRe: COUNTREG questions (40 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: COUNTREG questions (127 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (98 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: COUNTREG questions (83 lines) From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU> Re: COUNTREG questions (67 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> COUNTREG questions (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Changing type and length of multiple variablesRe: Changing type and length of multiple variables (132 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Changing type and length of multiple variables (92 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Changing type and length of multiple variables (32 lines) From: William Krause <wkrause2003@YAHOO.COM> Character Date Conversion in PROC SQLRe: Character Date Conversion in PROC SQL (65 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Character Date Conversion in PROC SQL (44 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Character Date Conversion in PROC SQL (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Character Date Conversion in PROC SQL (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Changing type and length of multiple variablesRe: Changing type and length of multiple variables (132 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Changing type and length of multiple variables (92 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Changing type and length of multiple variables (32 lines) From: William Krause <wkrause2003@YAHOO.COM> Character Date Conversion in PROC SQLRe: Character Date Conversion in PROC SQL (65 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Character Date Conversion in PROC SQL (44 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Character Date Conversion in PROC SQL (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Character Date Conversion in PROC SQL (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Character Date Conversion in PROC SQLRe: Character Date Conversion in PROC SQL (65 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Character Date Conversion in PROC SQL (44 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Character Date Conversion in PROC SQL (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Character Date Conversion in PROC SQL (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED?Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (43 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (174 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (115 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (101 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (36 lines) From: Adam Smith <raptorbio@HOTMAIL.COM> Re: Clustered discrete event time analysis - GENMOD vs. GLIMMIX vs. NLMIXED? (302 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Combining iterative DO and UNTIL conditionRe: Combining iterative DO and UNTIL condition (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Combining iterative DO and UNTIL condition (105 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Combining iterative DO and UNTIL condition (115 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Combining iterative DO and UNTIL condition (77 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Comparing means of group with unequal varianceRe: Comparing means of group with unequal variance (113 lines) From: syk ghb <sghb02@GMAIL.COM> Re: Comparing means of group with unequal variance (77 lines) From: Robin R High <rhigh@UNMC.EDU> Comparing means of group with unequal variance (28 lines) From: syk ghb <sghb02@GMAIL.COM> Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Computation of Attributable Risks and their Confidence Interval via logistic regressionRe: Computation of Attributable Risks and their Confidence Interval via logistic regression (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Computation of Attributable Risks and their Confidence Interval via logistic regression (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
CounterRe: Counter (127 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Counter (147 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Counter (131 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Counter (116 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (81 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Counter (7 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Re: Counter (104 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Counter (59 lines) From: SUBSCRIBE SAS-L Anonymous <hari.sas.j@GMAIL.COM> Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Covariate-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (192 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Covariate-adjusted ROC Curves using proc logistic in SAS 9.2? (119 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Covariated-adjusted ROC Curves using proc logistic in SAS 9.2?Re: Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (102 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Covariated-adjusted ROC Curves using proc logistic in SAS 9.2? (39 lines) From: Kim Fernandes <kim.fernandes@GMAIL.COM> DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
DATE FormatRe: DATE Format (41 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: DATE Format (41 lines) From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV> DATE Format (45 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Data LogicRe: Data Logic (109 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Doubly repeated measures (time and depth)Doubly repeated measures (time and depth) (82 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
FW: Computation of Attributable Risks and their Confidence Interval via logistic regressionFW: Computation of Attributable Risks and their Confidence Interval via logistic regression (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
FW: Is LEAVE "non-structured"?Re: FW: Is LEAVE "non-structured"? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> FW: Is LEAVE "non-structured"? (73 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> FW: Is LEAVE "non-structured"? (105 lines) From: Robert Rosofsky <Robert.Rosofsky@VERIZON.NET> FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
FW: SAS Global Forum 2011: Call for PapersFW: SAS Global Forum 2011: Call for Papers (50 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
FW: Thoughts on nested comments?Re: FW: Thoughts on nested comments? (139 lines) From: Mary <mlhoward@AVALON.NET> FW: Thoughts on nested comments? (124 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Flag DifferencesRe: Flag Differences (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Flag Differences (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Flag Differences (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Flag Differences (35 lines) From: Data _null_; <iebupdte@GMAIL.COM> Flag Differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
GLIMMIX questionRe: GLIMMIX question (199 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (68 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Re: GLIMMIX question (52 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> GLIMMIX question (37 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Genmod and zero inflated modelsRe: Genmod and zero inflated models (140 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Genmod and zero inflated models (62 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Genmod and zero inflated models (211 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Genmod and zero inflated models (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Genmod and zero inflated models (45 lines) From: Jerry Davis <jwd@UGA.EDU> How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
How to code to calculate continuous 12 month periodRe: How to code to calculate continuous 12 month period (378 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: How to code to calculate continuous 12 month period (304 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (135 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (252 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (123 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (238 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (194 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (192 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (155 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to code to calculate continuous 12 month period (148 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: How to code to calculate continuous 12 month period (211 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (203 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to code to calculate continuous 12 month period (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to code to calculate continuous 12 month period (79 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> How to code to calculate continuous 12 month period (51 lines) From: Dave Brewer <david.brewer@UC.EDU> How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
How to compress multiple decimal pointsRe: How to compress multiple decimal points (152 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (145 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to compress multiple decimal points (95 lines) From: Dave Brewer <david.brewer@UC.EDU> Re: How to compress multiple decimal points (56 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
In search of a more efficient programIn search of a more efficient program (62 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: In search of a more efficient program (80 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: In search of a more efficient program (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: In search of a more efficient program (58 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In search of a more efficient program (63 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: In search of a more efficient program (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> In search of a more efficient program (31 lines) From: Andy Arnold <awasas@COX.NET> Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Inputing Missing ValueRe: Inputing Missing Value (85 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Inputing Missing Value (67 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Inputing Missing Value (57 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Inputing Missing Value (24 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Inputing Missing Value (48 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Is LEAVE "non-structured"?Re: Is LEAVE "non-structured"? (23 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Is LEAVE "non-structured"? (94 lines) From: Ian Whitlock <iw1sas@GMAIL.COM> Re: Is LEAVE "non-structured"? (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Is LEAVE "non-structured"? (65 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is LEAVE "non-structured"? (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Is LEAVE "non-structured"? (70 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is LEAVE "non-structured"? (35 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Is LEAVE "non-structured"? (19 lines) From: Data _null_; <iebupdte@GMAIL.COM> Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Job Opening for Lead StatisticianJob Opening for Lead Statistician (44 lines) From: Tim Champney <tchampney@STRATEGICM.COM> Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Journal Style TableRe: Journal Style Table (63 lines) From: Nat Wooding <nathani@VERIZON.NET> Journal Style Table (23 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Macro errorRe: Macro error (37 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro error (123 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Macro error (13 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Macro error (97 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Macro error...Re: Macro error... (634 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (665 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro error... (599 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (547 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Macro error... (510 lines) From: MAHESH <peesari.mahesh@GMAIL.COM> Re: Macro error... (175 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Macro error... (144 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: Macro error... (148 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Macro error... (133 lines) From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM> NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
NLMIXED (Logistic Regression) - Estimate Statements & 95% CIsRe: NLMIXED (Logistic Regression) - Estimate Statements & 95% CIs (318 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Need to do a SQL join on fields of different data typesRe: Need to do a SQL join on fields of different data types (20 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (142 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Need to do a SQL join on fields of different data types (131 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> Re: Need to do a SQL join on fields of different data types (94 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Need to do a SQL join on fields of different data types (72 lines) From: Joe Matise <snoopy369@GMAIL.COM> Need to do a SQL join on fields of different data types (57 lines) From: Andrea Zimmerman <sassywench74va@GMAIL.COM> ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
ODS tagsets.RTFODS tagsets.RTF (18 lines) From: Paul <paulsrowland@YAHOO.COM> OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
OLAP Cube Minimum Cell SizeOLAP Cube Minimum Cell Size (27 lines) From: that statsguy <thatstatsguy@GMAIL.COM> OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
OT: Which Came First the DATA Step or the PROC?Re: OT: Which Came First the DATA Step or the PROC? (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: OT: Which Came First the DATA Step or the PROC? (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: Which Came First the DATA Step or the PROC? (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> OT: Which Came First the DATA Step or the PROC? (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Oracle xmltype columnRe: Oracle xmltype column (53 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Oracle xmltype column (27 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Re: Oracle xmltype column (10 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Oracle xmltype column (11 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Out of Office: July 21-27Out of Office: July 21-27 (11 lines) From: Chris Decker <cdecker@D-WISE.COM> Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Output of 2 Proc Reports in ODS RTFRe: Output of 2 Proc Reports in ODS RTF (616 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Output of 2 Proc Reports in ODS RTF (26 lines) From: Joe Matise <snoopy369@GMAIL.COM> Output of 2 Proc Reports in ODS RTF (13 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
PDF file size in SAS 9.2Re: PDF file size in SAS 9.2 (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: PDF file size in SAS 9.2 (89 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: PDF file size in SAS 9.2 (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PDF file size in SAS 9.2 (39 lines) From: Tom Robinson <barefootguru@GMAIL.COM> PDF file size in SAS 9.2 (25 lines) From: Vijayan Sundaram <vijchid@GMAIL.COM> PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
PROC GREPLAY ErrorPROC GREPLAY Error (121 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
PerformancePerformance (48 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Performance and disk write speedRe: Performance and disk write speed (77 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Performance and disk write speed (232 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Performance and disk write speed (217 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
PhUSE - September 28th Cambridge MAPhUSE - September 28th Cambridge MA (68 lines) From: Dan Boisvert <daniel.boisvert@GENZYME.COM> Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Proc Gchart HelpProc Gchart Help (39 lines) From: SAS_learner <proccontents@GMAIL.COM> Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Proc Report: Make the BY variable boldRe: Proc Report: Make the BY variable bold (91 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Proc Report: Make the BY variable bold (42 lines) From: Jake Adamson <Jake.Adamson@SQA.ORG.UK> Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Regarding date time valuesRegarding date time values (9 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: Regarding date time values (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Regarding date time values (13 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Searching for SSN stringRe: Searching for SSN string (97 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Searching for SSN string (81 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (105 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Searching for SSN string (84 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Searching for SSN string (91 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Searching for SSN string (66 lines) From: Annie Lee <hummingbird10111@HOTMAIL.COM> Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Securing passwordsRe: Securing passwords (154 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Securing passwords (89 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: Securing passwords (53 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Securing passwords (19 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Step-Wise Methods re-evaluatedRe: Step-Wise Methods re-evaluated (22 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (66 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Step-Wise Methods re-evaluated (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Step-Wise Methods re-evaluated (55 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Stepwise selection reduces multicollinearityRe: Stepwise selection reduces multicollinearity (47 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Re: Stepwise selection reduces multicollinearity (32 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Stepwise selection reduces multicollinearity (16 lines) From: goladin@gmail.com <goladin@GMAIL.COM> Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Submitting SAS jobs from cmd.exeRe: Submitting SAS jobs from cmd.exe (56 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Submitting SAS jobs from cmd.exe (40 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Submitting SAS jobs from cmd.exe (27 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Survival Analysis QuestionSurvival Analysis Question (66 lines) From: Andrew Agrimson <jagrimsasl@GMAIL.COM> Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Thoughts on nested comments?Re: Thoughts on nested comments? (148 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Thoughts on nested comments? (83 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (273 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (233 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Thoughts on nested comments? (163 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Thoughts on nested comments? (70 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Thoughts on nested comments? (100 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Thoughts on nested comments? (59 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Thoughts on nested comments? (113 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Thoughts on nested comments? (103 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Thoughts on nested comments? (71 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Time differencesRe: Time differences (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Time differences (35 lines) From: Randy <randistan69@HOTMAIL.COM> Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Update a dataset in use by other peopleRe: Update a dataset in use by other people (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Update a dataset in use by other people (30 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Updating tables being used by othersUpdating tables being used by others (42 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK> Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Weighted Least Squares Question in SASRe: Weighted Least Squares Question in SAS (147 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighted Least Squares Question in SAS (26 lines) From: Jon Matthews <jmatthews7101@YAHOO.COM> Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Why you should always use a RUN statement (A SAS Gotcha)Re: Why you should always use a RUN statement (A SAS Gotcha) (864 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (402 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (479 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (160 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (113 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (386 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (330 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (306 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (271 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Why you should always use a RUN statement (A SAS Gotcha) (235 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (30 lines) From: Proc Me <procme@CONCEPT-DELIVERY.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (195 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Why you should always use a RUN statement (A SAS Gotcha) (191 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (80 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (39 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (48 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Why you should always use a RUN statement (A SAS Gotcha) (157 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Why you should always use a RUN statement (A SAS Gotcha) (114 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (67 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Why you should always use a RUN statement (A SAS Gotcha) (143 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Why you should always use a RUN statement (A SAS Gotcha) (101 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
Windows SAS Install script wantedRe: Windows SAS Install script wanted (103 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Windows SAS Install script wanted (150 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Windows SAS Install script wanted (116 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Windows SAS Install script wanted (71 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
World Cup statisticsRe: World Cup statistics (81 lines) From: Charlie Shipp <charlie_shipp@MAC.COM> data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
data(read=)Re: data(read=) (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data(read=) (24 lines) From: Carlin, Justin M. <Carlin.Justin@MAYO.EDU> Re: data(read=) (8 lines) From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> data(read=) (32 lines) From: Justin Carlin <carlin.justin@MAYO.EDU> date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
date cleaning/conversionRe: date cleaning/conversion (97 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: date cleaning/conversion (99 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: date cleaning/conversion (96 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: date cleaning/conversion (64 lines) From: Franz <franz_cl2003@YAHOO.FR> Re: date cleaning/conversion (55 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: date cleaning/conversion (69 lines) From: toby dunn <tobydunn@HOTMAIL.COM> date cleaning/conversion (26 lines) From: Franz <franz_cl2003@YAHOO.FR> how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
how solve this this senario?Re: how solve this this senario? (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: how solve this this senario? (83 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> how solve this this senario? (39 lines) From: Nway <hymadsk@GMAIL.COM> how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
how to use SAS to simulate data in multifactor nested designhow to use SAS to simulate data in multifactor nested design (27 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
ordinal categorical longitudinal dataordinal categorical longitudinal data (26 lines) From: haiyan chen <haiyan_c@YAHOO.COM> parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
parsing infile from web URLRe: parsing infile from web URL (153 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: parsing infile from web URL (193 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: parsing infile from web URL (69 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: parsing infile from web URL (142 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: parsing infile from web URL (170 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> parsing infile from web URL (93 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
prx matching "all the characters are the same"Re: prx matching "all the characters are the same" (104 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: prx matching "all the characters are the same" (214 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (138 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (111 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: prx matching "all the characters are the same" (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (41 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: prx matching "all the characters are the same" (86 lines) From: toby dunn <tobydunn@HOTMAIL.COM> prx matching "all the characters are the same" (39 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
similar characteristics groupingRe: similar characteristics grouping (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar characteristics grouping (77 lines) From: toby dunn <tobydunn@HOTMAIL.COM> similar characteristics grouping (43 lines) From: M D <tant07@GMAIL.COM> similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
similar group identificationRe: similar group identification (89 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: similar group identification (17 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (76 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: similar group identification (52 lines) From: Dani Fdez <fdezdan@GMAIL.COM> Re: similar group identification (103 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> similar group identification (36 lines) From: M D <tant07@GMAIL.COM> stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
stepwise and colinearityRe: stepwise and colinearity (25 lines) From: goladin@gmail.com <goladin@GMAIL.COM> summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
summary statistics of all variablesRe: summary statistics of all variables (269 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (160 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (130 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (107 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (84 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: summary statistics of all variables (30 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: summary statistics of all variables (176 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: summary statistics of all variables (143 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: summary statistics of all variables (101 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: summary statistics of all variables (126 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: summary statistics of all variables (49 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: summary statistics of all variables (62 lines) From: Nat Wooding <nathani@VERIZON.NET> summary statistics of all variables (22 lines) From: Jeff <zhujp98@GMAIL.COM> trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
trend pattern in this data?Re: trend pattern in this data? (114 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: trend pattern in this data? (52 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: trend pattern in this data? (51 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> trend pattern in this data? (36 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
universal viewer 1.1Re: universal viewer 1.1 (87 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (98 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> Re: universal viewer 1.1 (78 lines) From: Andre Wielki <wielki@INED.FR> Re: universal viewer 1.1 (53 lines) From: Alan Churchill <alan.churchill@SAVIAN.NET> universal viewer 1.1 (33 lines) From: Andre Wielki <wielki@INED.FR> update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>
update a dataset in use by other peopleRe: update a dataset in use by other people (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (142 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: update a dataset in use by other people (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: update a dataset in use by other people (136 lines) From: Dee Karmaoui <dkarmaoui@BUSINESSDECISION.CO.UK>