Another concatenate within a data step questionAnother concatenate within a data step question (37 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Another concatenate within a data step question (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Another concatenate within a data step question (57 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Another concatenate within a data step question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Another concatenate within a data step question (114 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Conditional Macro - Wildcard ProblemsConditional Macro - Wildcard Problems (43 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Conditional Macro - Wildcard Problems (54 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Conditional Macro - Wildcard Problems (82 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Conditional Macro - Wildcard Problems (81 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Cumulative Accuracy Profile (CAP)Cumulative Accuracy Profile (CAP) (35 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Find MAX length of values of all character variables.Re: Find MAX length of values of all character variables. (107 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Find MAX length of values of all character variables. (115 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Find MAX length of values of all character variables. (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Find MAX length of values of all character variables. (129 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> GEE for between visit comparisonGEE for between visit comparison (20 lines) From: H Cheng <hcheng@RTI.ORG> Installing/running SAS 9.1.3 on Windows 7Installing/running SAS 9.1.3 on Windows 7 (26 lines) From: Rieza Soelaeman <rsoelaeman@GMAIL.COM> Most recent input data setMost recent input data set (18 lines) From: Daniel M <dmuenz@SDAC.HARVARD.EDU> Re: Most recent input data set (30 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Most recent input data set (51 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (73 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (71 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (84 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (102 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Most recent input data set (113 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (36 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> OT: SAS and its horrible no-good very bad software management systemOT: SAS and its horrible no-good very bad software management system (23 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: OT: SAS and its horrible no-good very bad software management system (72 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: OT: SAS and its horrible no-good very bad software management system (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: SAS and its horrible no-good very bad software management system (102 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> PROC APPEND problemRe: PROC APPEND problem (110 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (159 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: PROC APPEND problem (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> PRXMatch(): (.+) versus (.)PRXMatch(): (.+) versus (.) (65 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (113 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (83 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (166 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (162 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Passing single quotes nested inside double quotes with -initstmtPassing single quotes nested inside double quotes with -initstmt (49 lines) From: Joe Glover <tw925@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (65 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Passing single quotes nested inside double quotes with -initstmt (78 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (109 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
Conditional Macro - Wildcard ProblemsConditional Macro - Wildcard Problems (43 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Conditional Macro - Wildcard Problems (54 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Conditional Macro - Wildcard Problems (82 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Conditional Macro - Wildcard Problems (81 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Cumulative Accuracy Profile (CAP)Cumulative Accuracy Profile (CAP) (35 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Find MAX length of values of all character variables.Re: Find MAX length of values of all character variables. (107 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Find MAX length of values of all character variables. (115 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Find MAX length of values of all character variables. (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Find MAX length of values of all character variables. (129 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> GEE for between visit comparisonGEE for between visit comparison (20 lines) From: H Cheng <hcheng@RTI.ORG> Installing/running SAS 9.1.3 on Windows 7Installing/running SAS 9.1.3 on Windows 7 (26 lines) From: Rieza Soelaeman <rsoelaeman@GMAIL.COM> Most recent input data setMost recent input data set (18 lines) From: Daniel M <dmuenz@SDAC.HARVARD.EDU> Re: Most recent input data set (30 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Most recent input data set (51 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (73 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (71 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (84 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (102 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Most recent input data set (113 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (36 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> OT: SAS and its horrible no-good very bad software management systemOT: SAS and its horrible no-good very bad software management system (23 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: OT: SAS and its horrible no-good very bad software management system (72 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: OT: SAS and its horrible no-good very bad software management system (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: SAS and its horrible no-good very bad software management system (102 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> PROC APPEND problemRe: PROC APPEND problem (110 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (159 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: PROC APPEND problem (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> PRXMatch(): (.+) versus (.)PRXMatch(): (.+) versus (.) (65 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (113 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (83 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (166 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (162 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Passing single quotes nested inside double quotes with -initstmtPassing single quotes nested inside double quotes with -initstmt (49 lines) From: Joe Glover <tw925@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (65 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Passing single quotes nested inside double quotes with -initstmt (78 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (109 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
Cumulative Accuracy Profile (CAP)Cumulative Accuracy Profile (CAP) (35 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Find MAX length of values of all character variables.Re: Find MAX length of values of all character variables. (107 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Find MAX length of values of all character variables. (115 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Find MAX length of values of all character variables. (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Find MAX length of values of all character variables. (129 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> GEE for between visit comparisonGEE for between visit comparison (20 lines) From: H Cheng <hcheng@RTI.ORG> Installing/running SAS 9.1.3 on Windows 7Installing/running SAS 9.1.3 on Windows 7 (26 lines) From: Rieza Soelaeman <rsoelaeman@GMAIL.COM> Most recent input data setMost recent input data set (18 lines) From: Daniel M <dmuenz@SDAC.HARVARD.EDU> Re: Most recent input data set (30 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Most recent input data set (51 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (73 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (71 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (84 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (102 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Most recent input data set (113 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (36 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> OT: SAS and its horrible no-good very bad software management systemOT: SAS and its horrible no-good very bad software management system (23 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: OT: SAS and its horrible no-good very bad software management system (72 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: OT: SAS and its horrible no-good very bad software management system (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: SAS and its horrible no-good very bad software management system (102 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> PROC APPEND problemRe: PROC APPEND problem (110 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (159 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: PROC APPEND problem (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> PRXMatch(): (.+) versus (.)PRXMatch(): (.+) versus (.) (65 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (113 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (83 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (166 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (162 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Passing single quotes nested inside double quotes with -initstmtPassing single quotes nested inside double quotes with -initstmt (49 lines) From: Joe Glover <tw925@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (65 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Passing single quotes nested inside double quotes with -initstmt (78 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (109 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
Find MAX length of values of all character variables.Re: Find MAX length of values of all character variables. (107 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Find MAX length of values of all character variables. (115 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Find MAX length of values of all character variables. (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Find MAX length of values of all character variables. (129 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> GEE for between visit comparisonGEE for between visit comparison (20 lines) From: H Cheng <hcheng@RTI.ORG> Installing/running SAS 9.1.3 on Windows 7Installing/running SAS 9.1.3 on Windows 7 (26 lines) From: Rieza Soelaeman <rsoelaeman@GMAIL.COM> Most recent input data setMost recent input data set (18 lines) From: Daniel M <dmuenz@SDAC.HARVARD.EDU> Re: Most recent input data set (30 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Most recent input data set (51 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (73 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (71 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (84 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (102 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Most recent input data set (113 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (36 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> OT: SAS and its horrible no-good very bad software management systemOT: SAS and its horrible no-good very bad software management system (23 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: OT: SAS and its horrible no-good very bad software management system (72 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: OT: SAS and its horrible no-good very bad software management system (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: SAS and its horrible no-good very bad software management system (102 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> PROC APPEND problemRe: PROC APPEND problem (110 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (159 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: PROC APPEND problem (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> PRXMatch(): (.+) versus (.)PRXMatch(): (.+) versus (.) (65 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (113 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (83 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (166 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (162 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Passing single quotes nested inside double quotes with -initstmtPassing single quotes nested inside double quotes with -initstmt (49 lines) From: Joe Glover <tw925@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (65 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Passing single quotes nested inside double quotes with -initstmt (78 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (109 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
GEE for between visit comparisonGEE for between visit comparison (20 lines) From: H Cheng <hcheng@RTI.ORG> Installing/running SAS 9.1.3 on Windows 7Installing/running SAS 9.1.3 on Windows 7 (26 lines) From: Rieza Soelaeman <rsoelaeman@GMAIL.COM> Most recent input data setMost recent input data set (18 lines) From: Daniel M <dmuenz@SDAC.HARVARD.EDU> Re: Most recent input data set (30 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Most recent input data set (51 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (73 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (71 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (84 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (102 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Most recent input data set (113 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (36 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> OT: SAS and its horrible no-good very bad software management systemOT: SAS and its horrible no-good very bad software management system (23 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: OT: SAS and its horrible no-good very bad software management system (72 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: OT: SAS and its horrible no-good very bad software management system (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: SAS and its horrible no-good very bad software management system (102 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> PROC APPEND problemRe: PROC APPEND problem (110 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (159 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: PROC APPEND problem (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> PRXMatch(): (.+) versus (.)PRXMatch(): (.+) versus (.) (65 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (113 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (83 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (166 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (162 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Passing single quotes nested inside double quotes with -initstmtPassing single quotes nested inside double quotes with -initstmt (49 lines) From: Joe Glover <tw925@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (65 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Passing single quotes nested inside double quotes with -initstmt (78 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (109 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
Installing/running SAS 9.1.3 on Windows 7Installing/running SAS 9.1.3 on Windows 7 (26 lines) From: Rieza Soelaeman <rsoelaeman@GMAIL.COM> Most recent input data setMost recent input data set (18 lines) From: Daniel M <dmuenz@SDAC.HARVARD.EDU> Re: Most recent input data set (30 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Most recent input data set (51 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (73 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (71 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (84 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (102 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Most recent input data set (113 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (36 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> OT: SAS and its horrible no-good very bad software management systemOT: SAS and its horrible no-good very bad software management system (23 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: OT: SAS and its horrible no-good very bad software management system (72 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: OT: SAS and its horrible no-good very bad software management system (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: SAS and its horrible no-good very bad software management system (102 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> PROC APPEND problemRe: PROC APPEND problem (110 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (159 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: PROC APPEND problem (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> PRXMatch(): (.+) versus (.)PRXMatch(): (.+) versus (.) (65 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (113 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (83 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (166 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (162 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Passing single quotes nested inside double quotes with -initstmtPassing single quotes nested inside double quotes with -initstmt (49 lines) From: Joe Glover <tw925@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (65 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Passing single quotes nested inside double quotes with -initstmt (78 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (109 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
Most recent input data setMost recent input data set (18 lines) From: Daniel M <dmuenz@SDAC.HARVARD.EDU> Re: Most recent input data set (30 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Most recent input data set (51 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (73 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (71 lines) From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV> Re: Most recent input data set (84 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (102 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Most recent input data set (113 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Most recent input data set (36 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> OT: SAS and its horrible no-good very bad software management systemOT: SAS and its horrible no-good very bad software management system (23 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: OT: SAS and its horrible no-good very bad software management system (72 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: OT: SAS and its horrible no-good very bad software management system (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: SAS and its horrible no-good very bad software management system (102 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> PROC APPEND problemRe: PROC APPEND problem (110 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (159 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: PROC APPEND problem (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> PRXMatch(): (.+) versus (.)PRXMatch(): (.+) versus (.) (65 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (113 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (83 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (166 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (162 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Passing single quotes nested inside double quotes with -initstmtPassing single quotes nested inside double quotes with -initstmt (49 lines) From: Joe Glover <tw925@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (65 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Passing single quotes nested inside double quotes with -initstmt (78 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (109 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
OT: SAS and its horrible no-good very bad software management systemOT: SAS and its horrible no-good very bad software management system (23 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: OT: SAS and its horrible no-good very bad software management system (72 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: OT: SAS and its horrible no-good very bad software management system (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: OT: SAS and its horrible no-good very bad software management system (102 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> PROC APPEND problemRe: PROC APPEND problem (110 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (159 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: PROC APPEND problem (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> PRXMatch(): (.+) versus (.)PRXMatch(): (.+) versus (.) (65 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (113 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (83 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (166 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (162 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Passing single quotes nested inside double quotes with -initstmtPassing single quotes nested inside double quotes with -initstmt (49 lines) From: Joe Glover <tw925@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (65 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Passing single quotes nested inside double quotes with -initstmt (78 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (109 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
PROC APPEND problemRe: PROC APPEND problem (110 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (159 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC APPEND problem (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: PROC APPEND problem (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> PRXMatch(): (.+) versus (.)PRXMatch(): (.+) versus (.) (65 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (113 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (83 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (166 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (162 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Passing single quotes nested inside double quotes with -initstmtPassing single quotes nested inside double quotes with -initstmt (49 lines) From: Joe Glover <tw925@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (65 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Passing single quotes nested inside double quotes with -initstmt (78 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (109 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
PRXMatch(): (.+) versus (.)PRXMatch(): (.+) versus (.) (65 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (113 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (83 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (166 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: PRXMatch(): (.+) versus (.) (162 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: PRXMatch(): (.+) versus (.) (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Passing single quotes nested inside double quotes with -initstmtPassing single quotes nested inside double quotes with -initstmt (49 lines) From: Joe Glover <tw925@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (65 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Passing single quotes nested inside double quotes with -initstmt (78 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (109 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
Passing single quotes nested inside double quotes with -initstmtPassing single quotes nested inside double quotes with -initstmt (49 lines) From: Joe Glover <tw925@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (65 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Passing single quotes nested inside double quotes with -initstmt (78 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Passing single quotes nested inside double quotes with -initstmt (109 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
Proc Transpose and NamesProc Transpose and Names (24 lines) From: Brian T <dynamique@GMAIL.COM> Re: Proc Transpose and Names (38 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: Proc Transpose and Names (46 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc Transpose and Names (59 lines) From: Nat Wooding <nathani@VERIZON.NET> RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
RES: SEM & GMMRES: SEM & GMM (58 lines) From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR> RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLERe: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (52 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: RETRIEVE A SPECIFIC PART OF A ALPHA VARIABLE (96 lines) From: Nat Wooding <nathani@VERIZON.NET> SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
SAS and its horrible no-good very bad software management systemRe: SAS and its horrible no-good very bad software management system (42 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS and its horrible no-good very bad software management system (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (42 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: SAS and its horrible no-good very bad software management system (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SAS and its horrible no-good very bad software management system (76 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SAS and its horrible no-good very bad software management system (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
SAS created Excel files unreadable under Win 7Re: SAS created Excel files unreadable under Win 7 (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS created Excel files unreadable under Win 7 (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
SQL performanceRe: SQL performance (92 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
Sample size clinical trialsSample size clinical trials (23 lines) From: adel F. <adel_tangi@YAHOO.FR> Re: Sample size clinical trials (57 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
What is the Perl metacharacter for a page break character?What is the Perl metacharacter for a page break character? (67 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: What is the Perl metacharacter for a page break character? (145 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (31 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (40 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (53 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: What is the Perl metacharacter for a page break character? (121 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: What is the Perl metacharacter for a page break character? (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
creating a stringRe: creating a string (61 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: creating a string (113 lines) From: Mike Zdeb <msz03@ALBANY.EDU> how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
how to suppress the output of proc mixhow to suppress the output of proc mix (19 lines) From: Jeff <zhujp98@GMAIL.COM> Re: how to suppress the output of proc mix (49 lines) From: Robin R High <rhigh@UNMC.EDU> Re: how to suppress the output of proc mix (30 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> Re: how to suppress the output of proc mix (59 lines) From: Jeff <zhujp98@GMAIL.COM> macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
macro parameter combinationsRe: macro parameter combinations (140 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: macro parameter combinations (162 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
performance between libname and pass-throughRe: performance between libname and pass-through (35 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (36 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: performance between libname and pass-through (63 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (103 lines) From: Michael Davis <michael@BASSETTCONSULTING.COM> Re: performance between libname and pass-through (120 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: performance between libname and pass-through (80 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: performance between libname and pass-through (112 lines) From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM> random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>
random vs fixed effects proc mixedrandom vs fixed effects proc mixed (44 lines) From: anna Tsui <ascui@UIC.EDU>