=?windows-1252?Q?Re=3A_Report_=96_Alignment_=28_LINE_=29?==?windows-1252?Q?Re=3A_Report_=96_Alignment_=28_LINE_=29?= (117 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> =?windows-1252?Q?Report_=96_Alignment_=28_LINE_=29?==?windows-1252?Q?Report_=96_Alignment_=28_LINE_=29?= (103 lines) From: saslearn chicago <sasswamy@GMAIL.COM> Analyzing Large Data Sets, Sample Size Determination. Early Bird Discounts End June 19thAnalyzing Large Data Sets, Sample Size Determination. Early Bird Discounts End June 19th (49 lines) From: Dorothy Middleton <courses@STATCOURSE.COM> Re: Analyzing Large Data Sets, Sample Size Determination. Early Bird Discounts End June 19th (56 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Automatic reply: SAS-L Digest - 10 Jun 2010 - Special issue (#2010-709)Automatic reply: SAS-L Digest - 10 Jun 2010 - Special issue (#2010-709) (17 lines) From: Shelley Mitchell <Shelley.Mitchell@SAS.COM> Calculation of pseudo r square and AUROC using survey logistic statementCalculation of pseudo r square and AUROC using survey logistic statement (13 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Capitalize values in multiple variables in a SAS datasetCapitalize values in multiple variables in a SAS dataset (16 lines) From: William Krause <wkrause2003@YAHOO.COM> Re: Capitalize values in multiple variables in a SAS dataset (28 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Capitalize values in multiple variables in a SAS dataset (57 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (92 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Capitalize values in multiple variables in a SAS dataset (133 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: Capitalize values in multiple variables in a SAS dataset (161 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Capitalize values in multiple variables in a SAS dataset (94 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (189 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (78 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> DSNCATLGD FunctionDSNCATLGD Function (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: DSNCATLGD Function (35 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: DSNCATLGD Function (55 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: DSNCATLGD Function (57 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Data Step Update of MS Access Table: Is it possible?Data Step Update of MS Access Table: Is it possible? (99 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (114 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (131 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Data Step Update of MS Access Table: Is it possible? (141 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (154 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Define urban/rural by zip codeDefine urban/rural by zip code (16 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Define urban/rural by zip code (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Define urban/rural by zip code (25 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Define urban/rural by zip code (19 lines) From: BJ Mattson <bj.mattson@ODH.OHIO.GOV> Re: Define urban/rural by zip code (41 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Documentation for ODS GRAPHICS options?Documentation for ODS GRAPHICS options? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Documentation for ODS GRAPHICS options? (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Documentation for ODS GRAPHICS options? (58 lines) From: WIELKI Andre <wielki@INED.FR> Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
=?windows-1252?Q?Report_=96_Alignment_=28_LINE_=29?==?windows-1252?Q?Report_=96_Alignment_=28_LINE_=29?= (103 lines) From: saslearn chicago <sasswamy@GMAIL.COM> Analyzing Large Data Sets, Sample Size Determination. Early Bird Discounts End June 19thAnalyzing Large Data Sets, Sample Size Determination. Early Bird Discounts End June 19th (49 lines) From: Dorothy Middleton <courses@STATCOURSE.COM> Re: Analyzing Large Data Sets, Sample Size Determination. Early Bird Discounts End June 19th (56 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Automatic reply: SAS-L Digest - 10 Jun 2010 - Special issue (#2010-709)Automatic reply: SAS-L Digest - 10 Jun 2010 - Special issue (#2010-709) (17 lines) From: Shelley Mitchell <Shelley.Mitchell@SAS.COM> Calculation of pseudo r square and AUROC using survey logistic statementCalculation of pseudo r square and AUROC using survey logistic statement (13 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Capitalize values in multiple variables in a SAS datasetCapitalize values in multiple variables in a SAS dataset (16 lines) From: William Krause <wkrause2003@YAHOO.COM> Re: Capitalize values in multiple variables in a SAS dataset (28 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Capitalize values in multiple variables in a SAS dataset (57 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (92 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Capitalize values in multiple variables in a SAS dataset (133 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: Capitalize values in multiple variables in a SAS dataset (161 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Capitalize values in multiple variables in a SAS dataset (94 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (189 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (78 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> DSNCATLGD FunctionDSNCATLGD Function (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: DSNCATLGD Function (35 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: DSNCATLGD Function (55 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: DSNCATLGD Function (57 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Data Step Update of MS Access Table: Is it possible?Data Step Update of MS Access Table: Is it possible? (99 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (114 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (131 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Data Step Update of MS Access Table: Is it possible? (141 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (154 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Define urban/rural by zip codeDefine urban/rural by zip code (16 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Define urban/rural by zip code (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Define urban/rural by zip code (25 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Define urban/rural by zip code (19 lines) From: BJ Mattson <bj.mattson@ODH.OHIO.GOV> Re: Define urban/rural by zip code (41 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Documentation for ODS GRAPHICS options?Documentation for ODS GRAPHICS options? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Documentation for ODS GRAPHICS options? (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Documentation for ODS GRAPHICS options? (58 lines) From: WIELKI Andre <wielki@INED.FR> Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Analyzing Large Data Sets, Sample Size Determination. Early Bird Discounts End June 19thAnalyzing Large Data Sets, Sample Size Determination. Early Bird Discounts End June 19th (49 lines) From: Dorothy Middleton <courses@STATCOURSE.COM> Re: Analyzing Large Data Sets, Sample Size Determination. Early Bird Discounts End June 19th (56 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Automatic reply: SAS-L Digest - 10 Jun 2010 - Special issue (#2010-709)Automatic reply: SAS-L Digest - 10 Jun 2010 - Special issue (#2010-709) (17 lines) From: Shelley Mitchell <Shelley.Mitchell@SAS.COM> Calculation of pseudo r square and AUROC using survey logistic statementCalculation of pseudo r square and AUROC using survey logistic statement (13 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Capitalize values in multiple variables in a SAS datasetCapitalize values in multiple variables in a SAS dataset (16 lines) From: William Krause <wkrause2003@YAHOO.COM> Re: Capitalize values in multiple variables in a SAS dataset (28 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Capitalize values in multiple variables in a SAS dataset (57 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (92 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Capitalize values in multiple variables in a SAS dataset (133 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: Capitalize values in multiple variables in a SAS dataset (161 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Capitalize values in multiple variables in a SAS dataset (94 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (189 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (78 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> DSNCATLGD FunctionDSNCATLGD Function (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: DSNCATLGD Function (35 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: DSNCATLGD Function (55 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: DSNCATLGD Function (57 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Data Step Update of MS Access Table: Is it possible?Data Step Update of MS Access Table: Is it possible? (99 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (114 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (131 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Data Step Update of MS Access Table: Is it possible? (141 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (154 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Define urban/rural by zip codeDefine urban/rural by zip code (16 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Define urban/rural by zip code (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Define urban/rural by zip code (25 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Define urban/rural by zip code (19 lines) From: BJ Mattson <bj.mattson@ODH.OHIO.GOV> Re: Define urban/rural by zip code (41 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Documentation for ODS GRAPHICS options?Documentation for ODS GRAPHICS options? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Documentation for ODS GRAPHICS options? (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Documentation for ODS GRAPHICS options? (58 lines) From: WIELKI Andre <wielki@INED.FR> Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Automatic reply: SAS-L Digest - 10 Jun 2010 - Special issue (#2010-709)Automatic reply: SAS-L Digest - 10 Jun 2010 - Special issue (#2010-709) (17 lines) From: Shelley Mitchell <Shelley.Mitchell@SAS.COM> Calculation of pseudo r square and AUROC using survey logistic statementCalculation of pseudo r square and AUROC using survey logistic statement (13 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Capitalize values in multiple variables in a SAS datasetCapitalize values in multiple variables in a SAS dataset (16 lines) From: William Krause <wkrause2003@YAHOO.COM> Re: Capitalize values in multiple variables in a SAS dataset (28 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Capitalize values in multiple variables in a SAS dataset (57 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (92 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Capitalize values in multiple variables in a SAS dataset (133 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: Capitalize values in multiple variables in a SAS dataset (161 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Capitalize values in multiple variables in a SAS dataset (94 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (189 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (78 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> DSNCATLGD FunctionDSNCATLGD Function (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: DSNCATLGD Function (35 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: DSNCATLGD Function (55 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: DSNCATLGD Function (57 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Data Step Update of MS Access Table: Is it possible?Data Step Update of MS Access Table: Is it possible? (99 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (114 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (131 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Data Step Update of MS Access Table: Is it possible? (141 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (154 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Define urban/rural by zip codeDefine urban/rural by zip code (16 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Define urban/rural by zip code (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Define urban/rural by zip code (25 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Define urban/rural by zip code (19 lines) From: BJ Mattson <bj.mattson@ODH.OHIO.GOV> Re: Define urban/rural by zip code (41 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Documentation for ODS GRAPHICS options?Documentation for ODS GRAPHICS options? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Documentation for ODS GRAPHICS options? (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Documentation for ODS GRAPHICS options? (58 lines) From: WIELKI Andre <wielki@INED.FR> Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Calculation of pseudo r square and AUROC using survey logistic statementCalculation of pseudo r square and AUROC using survey logistic statement (13 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Capitalize values in multiple variables in a SAS datasetCapitalize values in multiple variables in a SAS dataset (16 lines) From: William Krause <wkrause2003@YAHOO.COM> Re: Capitalize values in multiple variables in a SAS dataset (28 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Capitalize values in multiple variables in a SAS dataset (57 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (92 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Capitalize values in multiple variables in a SAS dataset (133 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: Capitalize values in multiple variables in a SAS dataset (161 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Capitalize values in multiple variables in a SAS dataset (94 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (189 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (78 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> DSNCATLGD FunctionDSNCATLGD Function (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: DSNCATLGD Function (35 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: DSNCATLGD Function (55 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: DSNCATLGD Function (57 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Data Step Update of MS Access Table: Is it possible?Data Step Update of MS Access Table: Is it possible? (99 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (114 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (131 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Data Step Update of MS Access Table: Is it possible? (141 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (154 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Define urban/rural by zip codeDefine urban/rural by zip code (16 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Define urban/rural by zip code (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Define urban/rural by zip code (25 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Define urban/rural by zip code (19 lines) From: BJ Mattson <bj.mattson@ODH.OHIO.GOV> Re: Define urban/rural by zip code (41 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Documentation for ODS GRAPHICS options?Documentation for ODS GRAPHICS options? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Documentation for ODS GRAPHICS options? (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Documentation for ODS GRAPHICS options? (58 lines) From: WIELKI Andre <wielki@INED.FR> Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Capitalize values in multiple variables in a SAS datasetCapitalize values in multiple variables in a SAS dataset (16 lines) From: William Krause <wkrause2003@YAHOO.COM> Re: Capitalize values in multiple variables in a SAS dataset (28 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Capitalize values in multiple variables in a SAS dataset (57 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (92 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Capitalize values in multiple variables in a SAS dataset (133 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: Capitalize values in multiple variables in a SAS dataset (161 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Capitalize values in multiple variables in a SAS dataset (94 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Capitalize values in multiple variables in a SAS dataset (189 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (78 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> DSNCATLGD FunctionDSNCATLGD Function (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: DSNCATLGD Function (35 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: DSNCATLGD Function (55 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: DSNCATLGD Function (57 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Data Step Update of MS Access Table: Is it possible?Data Step Update of MS Access Table: Is it possible? (99 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (114 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (131 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Data Step Update of MS Access Table: Is it possible? (141 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (154 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Define urban/rural by zip codeDefine urban/rural by zip code (16 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Define urban/rural by zip code (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Define urban/rural by zip code (25 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Define urban/rural by zip code (19 lines) From: BJ Mattson <bj.mattson@ODH.OHIO.GOV> Re: Define urban/rural by zip code (41 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Documentation for ODS GRAPHICS options?Documentation for ODS GRAPHICS options? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Documentation for ODS GRAPHICS options? (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Documentation for ODS GRAPHICS options? (58 lines) From: WIELKI Andre <wielki@INED.FR> Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (78 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> DSNCATLGD FunctionDSNCATLGD Function (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: DSNCATLGD Function (35 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: DSNCATLGD Function (55 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: DSNCATLGD Function (57 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Data Step Update of MS Access Table: Is it possible?Data Step Update of MS Access Table: Is it possible? (99 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (114 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (131 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Data Step Update of MS Access Table: Is it possible? (141 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (154 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Define urban/rural by zip codeDefine urban/rural by zip code (16 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Define urban/rural by zip code (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Define urban/rural by zip code (25 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Define urban/rural by zip code (19 lines) From: BJ Mattson <bj.mattson@ODH.OHIO.GOV> Re: Define urban/rural by zip code (41 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Documentation for ODS GRAPHICS options?Documentation for ODS GRAPHICS options? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Documentation for ODS GRAPHICS options? (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Documentation for ODS GRAPHICS options? (58 lines) From: WIELKI Andre <wielki@INED.FR> Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
DSNCATLGD FunctionDSNCATLGD Function (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: DSNCATLGD Function (35 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: DSNCATLGD Function (55 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: DSNCATLGD Function (57 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: DSNCATLGD Function (77 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Data Step Update of MS Access Table: Is it possible?Data Step Update of MS Access Table: Is it possible? (99 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (114 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (131 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Data Step Update of MS Access Table: Is it possible? (141 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (154 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Define urban/rural by zip codeDefine urban/rural by zip code (16 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Define urban/rural by zip code (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Define urban/rural by zip code (25 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Define urban/rural by zip code (19 lines) From: BJ Mattson <bj.mattson@ODH.OHIO.GOV> Re: Define urban/rural by zip code (41 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Documentation for ODS GRAPHICS options?Documentation for ODS GRAPHICS options? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Documentation for ODS GRAPHICS options? (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Documentation for ODS GRAPHICS options? (58 lines) From: WIELKI Andre <wielki@INED.FR> Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Data Step Update of MS Access Table: Is it possible?Data Step Update of MS Access Table: Is it possible? (99 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (114 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (131 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Data Step Update of MS Access Table: Is it possible? (141 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Data Step Update of MS Access Table: Is it possible? (154 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Define urban/rural by zip codeDefine urban/rural by zip code (16 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Define urban/rural by zip code (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Define urban/rural by zip code (25 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Define urban/rural by zip code (19 lines) From: BJ Mattson <bj.mattson@ODH.OHIO.GOV> Re: Define urban/rural by zip code (41 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Documentation for ODS GRAPHICS options?Documentation for ODS GRAPHICS options? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Documentation for ODS GRAPHICS options? (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Documentation for ODS GRAPHICS options? (58 lines) From: WIELKI Andre <wielki@INED.FR> Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Define urban/rural by zip codeDefine urban/rural by zip code (16 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Define urban/rural by zip code (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Define urban/rural by zip code (25 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Define urban/rural by zip code (19 lines) From: BJ Mattson <bj.mattson@ODH.OHIO.GOV> Re: Define urban/rural by zip code (41 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Documentation for ODS GRAPHICS options?Documentation for ODS GRAPHICS options? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Documentation for ODS GRAPHICS options? (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Documentation for ODS GRAPHICS options? (58 lines) From: WIELKI Andre <wielki@INED.FR> Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Documentation for ODS GRAPHICS options?Documentation for ODS GRAPHICS options? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Documentation for ODS GRAPHICS options? (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Documentation for ODS GRAPHICS options? (58 lines) From: WIELKI Andre <wielki@INED.FR> Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Drop a renamed variable using the drop statementDrop a renamed variable using the drop statement (35 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (61 lines) From: SAS For Us <sasforusandmore@GMAIL.COM> Re: Drop a renamed variable using the drop statement (77 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (57 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Drop a renamed variable using the drop statement (56 lines) From: Andre Wielki <wielki@INED.FR> Re: Drop a renamed variable using the drop statement (114 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Drop a renamed variable using the drop statement (154 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Errors in log to output fileErrors in log to output file (11 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (31 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (24 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Errors in log to output file (59 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Errors in log to output file (13 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Re: Errors in log to output file (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: Errors in log to output file (22 lines) From: Craig Johnson <cjohns38@GMAIL.COM> Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Export to Excel by yearsExport to Excel by years (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (62 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (84 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Export to Excel by years (142 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Export to Excel by years (7 lines) From: Kim Brown <kibrown@LADHS.ORG> Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Extracting and reformatting dataExtracting and reformatting data (82 lines) From: Sid N <nsid31@GMAIL.COM> Re: Extracting and reformatting data (183 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Filling in Missing ObservationsFilling in Missing Observations (55 lines) From: Randy <randistan69@HOTMAIL.COM> Re: Filling in Missing Observations (125 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Help - how to create/use sha1 hash in SASHelp - how to create/use sha1 hash in SAS (27 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: Help - how to create/use sha1 hash in SAS (85 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Help - how to create/use sha1 hash in SAS (100 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Help me use a macro and avoid all this copy-pasteHelp me use a macro and avoid all this copy-paste (38 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (59 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: Help me use a macro and avoid all this copy-paste (74 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: Help me use a macro and avoid all this copy-paste (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Help with Graphs ( Proc Gplot)Help with Graphs ( Proc Gplot) (87 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Help with Graphs ( Proc Gplot) (40 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
How do I disable sort when creating a new dataset from another?Re: How do I disable sort when creating a new dataset from another? (59 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
How do I get specific abend or return code from SAS under UNIXHow do I get specific abend or return code from SAS under UNIX (32 lines) From: Scott Bennett <scott.bennett@HEWITT.COM> Re: How do I get specific abend or return code from SAS under UNIX (68 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: How do I get specific abend or return code from SAS under UNIX (45 lines) From: Tom Robinson <barefootguru@GMAIL.COM> Re: How do I get specific abend or return code from SAS under UNIX (66 lines) From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM> Re: How do I get specific abend or return code from SAS under UNIX (79 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
How to calculate the Confidence interval for ICC for a three level model with only random effect ?How to calculate the Confidence interval for ICC for a three level model with only random effect ? (19 lines) From: Wong, Lee-Yang (CDC/ONDIEH/NCEH) <lyw8@CDC.GOV> How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
How to capture return code in sas9.2 batch mode on windows?How to capture return code in sas9.2 batch mode on windows? (32 lines) From: W. Matthew Wilson <matt@TPLUS1.COM> Re: How to capture return code in sas9.2 batch mode on windows? (159 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to capture return code in sas9.2 batch mode on windows? (15 lines) From: Phil Rack <philrack@MINEQUEST.COM> ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
ISO8601 date conversion macroISO8601 date conversion macro (466 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Inconsistent Failure to Detect Committed DeletesInconsistent Failure to Detect Committed Deletes (105 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: Inconsistent Failure to Detect Committed Deletes (115 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inconsistent Failure to Detect Committed Deletes (133 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Inserting a table in an ODS REGION?Inserting a table in an ODS REGION? (44 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (27 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (64 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (81 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Inserting a table in an ODS REGION? (28 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (31 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (41 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (38 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Inserting a table in an ODS REGION? (59 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (76 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (84 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Inserting a table in an ODS REGION? (98 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (107 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Inserting a table in an ODS REGION? (134 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Re: Inserting a table in an ODS REGION? (66 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Job Posting, Associate Director of StatisticsJob Posting, Associate Director of Statistics (153 lines) From: Joe Carpenter <Joe@VTOXFORD.ORG> Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Join SQL table with a SAS dataset?Re: Join SQL table with a SAS dataset? (97 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Last Reminder: Two Live, Interactive, Online June SEM WorkshopsLast Reminder: Two Live, Interactive, Online June SEM Workshops (63 lines) From: Geoffrey Hubona <ghubona@CIS.GSU.EDU> Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Last quarterLast quarter (22 lines) From: Pareen <mditconsult@GMAIL.COM> Re: Last quarter (40 lines) From: Nat Wooding <nathani@VERIZON.NET> LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
LoopRe: Loop (78 lines) From: Richard A. DeVenezia <rdevenezia@GMAIL.COM> Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Models in hedge fundsModels in hedge funds (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Models in hedge funds (25 lines) From: Chung Y. Li <li.chungying@GMAIL.COM> NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
NOPRINT option for SUBMIT CONTINUE SQL in SAS/AFNOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (48 lines) From: Kevin Myers <kmyers1@CLEARWIRE.NET> Re: NOPRINT option for SUBMIT CONTINUE SQL in SAS/AF (67 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Nonzero min valueNonzero min value (34 lines) From: Yingtao <yingtaoliu@GMAIL.COM> Re: Nonzero min value (97 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Nonzero min value (91 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Nonzero min value (102 lines) From: Yingtao <yingtaoliu@GMAIL.COM> ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
ODBC, Excel, and headersODBC, Excel, and headers (44 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ODBC, Excel, and headers (59 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
OT: Thursday TheoryOT: Thursday Theory (26 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> OT: Thursday Theory (40 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: OT: Thursday Theory (46 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: OT: Thursday Theory (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Thursday Theory (57 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Thursday Theory (80 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: OT: Thursday Theory (53 lines) From: Viel, Kevin <kviel@SJHA.ORG> Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Optimizing Multiple Objectives ---GA procedureOptimizing Multiple Objectives ---GA procedure (11 lines) From: Clark An <kuhasu@126.COM> PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
PROC Report – 2 SetsPROC Report – 2 Sets (82 lines) From: SAS Swamy <sasswamy@GMAIL.COM> Re: PROC Report – 2 Sets (103 lines) From: Ya Huang <ya.huang@AMYLIN.COM> PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
PROC SORT/ No disk space available for the write operationPROC SORT/ No disk space available for the write operation (25 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (44 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC SORT/ No disk space available for the write operation (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (15 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SORT/ No disk space available for the write operation (91 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: PROC SORT/ No disk space available for the write operation (95 lines) From: Subscribe Sas-L Jkr <jayakumarreddy@GMAIL.COM> Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Proc Export to Microsoft Access Database: Poor PerformanceRe: Proc Export to Microsoft Access Database: Poor Performance (112 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (130 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (215 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proc Export to Microsoft Access Database: Poor Performance (187 lines) From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (254 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (276 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (295 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Proc Export to Microsoft Access Database: Poor Performance (377 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Proc Export to Microsoft Access Database: Poor Performance (118 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Proc Genmod running for 17 hoursProc Genmod running for 17 hours (15 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (27 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: Proc Genmod running for 17 hours (24 lines) From: Jeff Magouirk <jeffrey.magouirk@RMPDC.ORG> Re: Proc Genmod running for 17 hours (58 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Proper reliability ICC modelProper reliability ICC model (28 lines) From: Simcha Pollack <simcha.pollack@CHSLI.ORG> Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Question about SAS macro variables and PROC PMENURe: Question about SAS macro variables and PROC PMENU (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Question about SAS macro variables and PROC PMENU (105 lines) From: Chi Shu <chichi_cn@LIVE.COM> Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Repeated I/O errorsRepeated I/O errors (17 lines) From: HÃ¥kan Lane <hlane@CLS.DK> Re: Repeated I/O errors (60 lines) From: Viel, Kevin <kviel@SJHA.ORG> Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Root finding in SASRoot finding in SAS (47 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
SAS Programmer San FranciscoSAS Programmer San Francisco (12 lines) From: Amir <docwriter@GMAIL.COM> SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
SAS oddities and spiders from MarsRe: SAS oddities and spiders from Mars (63 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
SAS output gives 0 and dotsSAS output gives 0 and dots (16 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (58 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: SAS output gives 0 and dots (73 lines) From: Robin R High <rhigh@UNMC.EDU> Re: SAS output gives 0 and dots (196 lines) From: Leonard Rusinamhodzi <leomhodzy@YAHOO.CO.UK> Re: SAS output gives 0 and dots (236 lines) From: Robin R High <rhigh@UNMC.EDU> SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
SAS-L: Directory of SASHELP datasets?SAS-L: Directory of SASHELP datasets? (18 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (50 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (85 lines) From: Mira J. Shapiro <mirashapir@AOL.COM> Re: SAS-L: Directory of SASHELP datasets? (103 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (146 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: SAS-L: Directory of SASHELP datasets? (73 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (79 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: SAS-L: Directory of SASHELP datasets? (27 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS-L: Directory of SASHELP datasets? (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: SAS-L: Directory of SASHELP datasets? (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: SAS-L: Directory of SASHELP datasets? (138 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
SG Graph Box Plot QuestionSG Graph Box Plot Question (82 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Re: SG Graph Box Plot Question (201 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (214 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: SG Graph Box Plot Question (119 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (166 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: SG Graph Box Plot Question (177 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SG Graph Box Plot Question (187 lines) From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM> Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Skill Sets needed to be considered a SAS programmerSkill Sets needed to be considered a SAS programmer (44 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Skill Sets needed to be considered a SAS programmer (82 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Skill Sets needed to be considered a SAS programmer (96 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Mary <mlhoward@AVALON.NET> Re: Skill Sets needed to be considered a SAS programmer (107 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (74 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Skill Sets needed to be considered a SAS programmer (50 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Skill Sets needed to be considered a SAS programmer (135 lines) From: SAS_learner <proccontents@GMAIL.COM> Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Solve non-linear equationSolve non-linear equation (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: Solve non-linear equation (79 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Stacked Bar Graph Value labelsStacked Bar Graph Value labels (50 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Re: Stacked Bar Graph Value labels (139 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Using sysdate9. in where statementUsing sysdate9. in where statement (30 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (74 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (95 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (103 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Using sysdate9. in where statement (122 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Using sysdate9. in where statement (70 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Using the CONTRAST Statement in PROC MIXED for 3 fixed effectsUsing the CONTRAST Statement in PROC MIXED for 3 fixed effects (95 lines) From: Anne <anne.daubmann@GMX.DE> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (118 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Re: Using the CONTRAST Statement in PROC MIXED for 3 fixed effects (248 lines) From: Robin R High <rhigh@UNMC.EDU> Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
Windows 7 and SASRe: Windows 7 and SAS (64 lines) From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM> ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
ZERO RECORDZERO RECORD (10 lines) From: Jeff <zhujp98@GMAIL.COM> Re: ZERO RECORD (62 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
bootstrapping for overfit models?bootstrapping for overfit models? (25 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (44 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: bootstrapping for overfit models? (40 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: bootstrapping for overfit models? (17 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> Re: bootstrapping for overfit models? (54 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
calculating confidence intervals for interaction termscalculating confidence intervals for interaction terms (14 lines) From: Vishal Bali <v.bali4u@GMAIL.COM> Re: calculating confidence intervals for interaction terms (32 lines) From: Robert Feyerharm <robertf@HEALTH.OK.GOV> call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
call routine vs analogous function - when is one better than the other?call routine vs analogous function - when is one better than the other? (33 lines) From: Jennifer R. Holdcraft <jrholdcraft@AEP.COM> Re: call routine vs analogous function - when is one better than the other? (90 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: call routine vs analogous function - when is one better than the other? (48 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: call routine vs analogous function - when is one better than the other? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
how to solve this senario?how to solve this senario? (33 lines) From: nway <hymadsk@GMAIL.COM> Re: how to solve this senario? (60 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
proc gchart warning messageproc gchart warning message (20 lines) From: carolyn <caroln_1999@YAHOO.COM> proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
proc loess - out of memoryproc loess - out of memory (17 lines) From: Robert Feyerharm <RobertF@HEALTH.OK.GOV> Re: proc loess - out of memory (43 lines) From: Murphy Choy <goladin@GMAIL.COM> proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
proc means and pennies...proc means and pennies... (43 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: proc means and pennies... (71 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: proc means and pennies... (94 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
request references: SQL list processingRe: request references: SQL list processing (23 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (49 lines) From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV> Re: request references: SQL list processing (54 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
tabulate questiontabulate question (87 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> Re: tabulate question (143 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: tabulate question (200 lines) From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV> when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>
when to do separate analysis for genderwhen to do separate analysis for gender (25 lines) From: Myung Ki <m.ki@UCL.AC.UK> Re: when to do separate analysis for gender (71 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: when to do separate analysis for gender (98 lines) From: Ryan Black <ryan.andrew.black@GMAIL.COM> Re: when to do separate analysis for gender (77 lines) From: Viel, Kevin <kviel@SJHA.ORG>