=?utf-8?B?UkU6IOWbnuWkje+8miBTdGF0aXN0aWNhbCBBbmFseXNpcyBIZWxw?==?utf-8?B?UkU6IOWbnuWkje+8miBTdGF0aXN0aWNhbCBBbmFseXNpcyBIZWxw?= (66 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> A Friday JokeA Friday Joke (7 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: A Friday Joke (18 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: A Friday Joke (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: A Friday Joke (76 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: A Friday Joke (87 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A Friday Joke (85 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A Friday Joke (96 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A Friday Joke (10 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: A Friday Joke (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: A Friday Joke (40 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: A Friday Joke (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: A Friday Joke (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: A Friday Joke (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: A Friday Joke (96 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: A Friday Joke (106 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: A Friday Joke (18 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: A Friday Joke (22 lines) From: .. <ajayohri@YAHOO.COM> Re: A Friday Joke (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: A Friday Joke (65 lines) From: Jiangtang Hu <jiangtanghu@GMAIL.COM> A good way to write out duplicates?A good way to write out duplicates? (31 lines) From: Sun <sunffang@YAHOO.COM> Re: A good way to write out duplicates? (22 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: A good way to write out duplicates? (60 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: A good way to write out duplicates? (49 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: A good way to write out duplicates? (49 lines) From: Arthur Tabachneck <art297@ROGERS.COM> A poem for statisticians and data analystsA poem for statisticians and data analysts (26 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Array......?Array......? (46 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (68 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Array......? (90 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (96 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Array......? (113 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (136 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (135 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (137 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (152 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Array......? (165 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Array......? (88 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Array......? (109 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (140 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Array......? (171 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Array......? (204 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Array......? (192 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472) (18 lines) From: Zais, Hans <Hans.Zais@PAREXEL.COM> Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: proc format bug?Automatic reply: proc format bug? (14 lines) From: Chris Hemedinger <Chris.Hemedinger@SAS.COM> Business Operations Analyst position open in Richmond, VA (USA)Business Operations Analyst position open in Richmond, VA (USA) (62 lines) From: Nat Wooding <nathani@VERIZON.NET> Can't run 9.3 compiled macro in 9.2Can't run 9.3 compiled macro in 9.2 (17 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (41 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Can't run 9.3 compiled macro in 9.2 (53 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (27 lines) From: Andre Wielki <wielki@INED.FR> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (11 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
A Friday JokeA Friday Joke (7 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: A Friday Joke (18 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: A Friday Joke (41 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: A Friday Joke (76 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: A Friday Joke (87 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A Friday Joke (85 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A Friday Joke (96 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A Friday Joke (10 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: A Friday Joke (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: A Friday Joke (40 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: A Friday Joke (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: A Friday Joke (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: A Friday Joke (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: A Friday Joke (96 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: A Friday Joke (106 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: A Friday Joke (18 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: A Friday Joke (22 lines) From: .. <ajayohri@YAHOO.COM> Re: A Friday Joke (56 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: A Friday Joke (65 lines) From: Jiangtang Hu <jiangtanghu@GMAIL.COM> A good way to write out duplicates?A good way to write out duplicates? (31 lines) From: Sun <sunffang@YAHOO.COM> Re: A good way to write out duplicates? (22 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: A good way to write out duplicates? (60 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: A good way to write out duplicates? (49 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: A good way to write out duplicates? (49 lines) From: Arthur Tabachneck <art297@ROGERS.COM> A poem for statisticians and data analystsA poem for statisticians and data analysts (26 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Array......?Array......? (46 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (68 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Array......? (90 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (96 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Array......? (113 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (136 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (135 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (137 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (152 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Array......? (165 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Array......? (88 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Array......? (109 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (140 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Array......? (171 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Array......? (204 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Array......? (192 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472) (18 lines) From: Zais, Hans <Hans.Zais@PAREXEL.COM> Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: proc format bug?Automatic reply: proc format bug? (14 lines) From: Chris Hemedinger <Chris.Hemedinger@SAS.COM> Business Operations Analyst position open in Richmond, VA (USA)Business Operations Analyst position open in Richmond, VA (USA) (62 lines) From: Nat Wooding <nathani@VERIZON.NET> Can't run 9.3 compiled macro in 9.2Can't run 9.3 compiled macro in 9.2 (17 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (41 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Can't run 9.3 compiled macro in 9.2 (53 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (27 lines) From: Andre Wielki <wielki@INED.FR> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (11 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
A good way to write out duplicates?A good way to write out duplicates? (31 lines) From: Sun <sunffang@YAHOO.COM> Re: A good way to write out duplicates? (22 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: A good way to write out duplicates? (60 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: A good way to write out duplicates? (49 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: A good way to write out duplicates? (49 lines) From: Arthur Tabachneck <art297@ROGERS.COM> A poem for statisticians and data analystsA poem for statisticians and data analysts (26 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Array......?Array......? (46 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (68 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Array......? (90 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (96 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Array......? (113 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (136 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (135 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (137 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (152 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Array......? (165 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Array......? (88 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Array......? (109 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (140 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Array......? (171 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Array......? (204 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Array......? (192 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472) (18 lines) From: Zais, Hans <Hans.Zais@PAREXEL.COM> Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: proc format bug?Automatic reply: proc format bug? (14 lines) From: Chris Hemedinger <Chris.Hemedinger@SAS.COM> Business Operations Analyst position open in Richmond, VA (USA)Business Operations Analyst position open in Richmond, VA (USA) (62 lines) From: Nat Wooding <nathani@VERIZON.NET> Can't run 9.3 compiled macro in 9.2Can't run 9.3 compiled macro in 9.2 (17 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (41 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Can't run 9.3 compiled macro in 9.2 (53 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (27 lines) From: Andre Wielki <wielki@INED.FR> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (11 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
A poem for statisticians and data analystsA poem for statisticians and data analysts (26 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Array......?Array......? (46 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (68 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Array......? (90 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (96 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Array......? (113 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (136 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (135 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (137 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (152 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Array......? (165 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Array......? (88 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Array......? (109 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (140 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Array......? (171 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Array......? (204 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Array......? (192 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472) (18 lines) From: Zais, Hans <Hans.Zais@PAREXEL.COM> Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: proc format bug?Automatic reply: proc format bug? (14 lines) From: Chris Hemedinger <Chris.Hemedinger@SAS.COM> Business Operations Analyst position open in Richmond, VA (USA)Business Operations Analyst position open in Richmond, VA (USA) (62 lines) From: Nat Wooding <nathani@VERIZON.NET> Can't run 9.3 compiled macro in 9.2Can't run 9.3 compiled macro in 9.2 (17 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (41 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Can't run 9.3 compiled macro in 9.2 (53 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (27 lines) From: Andre Wielki <wielki@INED.FR> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (11 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Array......?Array......? (46 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (68 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Array......? (90 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (96 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Array......? (113 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (136 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (135 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (137 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Array......? (152 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Array......? (165 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Array......? (88 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Array......? (109 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: Array......? (140 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Array......? (171 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Array......? (204 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Array......? (192 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472) (18 lines) From: Zais, Hans <Hans.Zais@PAREXEL.COM> Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: proc format bug?Automatic reply: proc format bug? (14 lines) From: Chris Hemedinger <Chris.Hemedinger@SAS.COM> Business Operations Analyst position open in Richmond, VA (USA)Business Operations Analyst position open in Richmond, VA (USA) (62 lines) From: Nat Wooding <nathani@VERIZON.NET> Can't run 9.3 compiled macro in 9.2Can't run 9.3 compiled macro in 9.2 (17 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (41 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Can't run 9.3 compiled macro in 9.2 (53 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (27 lines) From: Andre Wielki <wielki@INED.FR> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (11 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-472) (18 lines) From: Zais, Hans <Hans.Zais@PAREXEL.COM> Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: proc format bug?Automatic reply: proc format bug? (14 lines) From: Chris Hemedinger <Chris.Hemedinger@SAS.COM> Business Operations Analyst position open in Richmond, VA (USA)Business Operations Analyst position open in Richmond, VA (USA) (62 lines) From: Nat Wooding <nathani@VERIZON.NET> Can't run 9.3 compiled macro in 9.2Can't run 9.3 compiled macro in 9.2 (17 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (41 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Can't run 9.3 compiled macro in 9.2 (53 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (27 lines) From: Andre Wielki <wielki@INED.FR> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (11 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483)Automatic reply: SAS-L Digest - 21 Jun 2012 - Special issue (#2012-483) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: proc format bug?Automatic reply: proc format bug? (14 lines) From: Chris Hemedinger <Chris.Hemedinger@SAS.COM> Business Operations Analyst position open in Richmond, VA (USA)Business Operations Analyst position open in Richmond, VA (USA) (62 lines) From: Nat Wooding <nathani@VERIZON.NET> Can't run 9.3 compiled macro in 9.2Can't run 9.3 compiled macro in 9.2 (17 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (41 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Can't run 9.3 compiled macro in 9.2 (53 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (27 lines) From: Andre Wielki <wielki@INED.FR> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (11 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Automatic reply: proc format bug?Automatic reply: proc format bug? (14 lines) From: Chris Hemedinger <Chris.Hemedinger@SAS.COM> Business Operations Analyst position open in Richmond, VA (USA)Business Operations Analyst position open in Richmond, VA (USA) (62 lines) From: Nat Wooding <nathani@VERIZON.NET> Can't run 9.3 compiled macro in 9.2Can't run 9.3 compiled macro in 9.2 (17 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (41 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Can't run 9.3 compiled macro in 9.2 (53 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (27 lines) From: Andre Wielki <wielki@INED.FR> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (11 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Business Operations Analyst position open in Richmond, VA (USA)Business Operations Analyst position open in Richmond, VA (USA) (62 lines) From: Nat Wooding <nathani@VERIZON.NET> Can't run 9.3 compiled macro in 9.2Can't run 9.3 compiled macro in 9.2 (17 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (41 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Can't run 9.3 compiled macro in 9.2 (53 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (27 lines) From: Andre Wielki <wielki@INED.FR> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (11 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Can't run 9.3 compiled macro in 9.2Can't run 9.3 compiled macro in 9.2 (17 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (41 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Can't run 9.3 compiled macro in 9.2 (53 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Can't run 9.3 compiled macro in 9.2 (27 lines) From: Andre Wielki <wielki@INED.FR> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (11 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (11 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Correaltion CoefficientCorrealtion Coefficient (30 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Correaltion Coefficient (62 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Correaltion Coefficient (39 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Diversity and Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (142 lines) From: .. <ajayohri@YAHOO.COM> Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Erlang-C formulaErlang-C formula (21 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> Re: Erlang-C formula (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Erlang-C formula (60 lines) From: Ballach, John <John.Ballach@SALLIEMAE.COM> How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
How to categorise missing valuesHow to categorise missing values (51 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (74 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: How to categorise missing values (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to categorise missing values (12 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Re: How to categorise missing values (15 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
How to tell a directory from a file?How to tell a directory from a file? (75 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (104 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (114 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (132 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (198 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (236 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (249 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (260 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (277 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (334 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (292 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: How to tell a directory from a file? (354 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (433 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (420 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (421 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (491 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (482 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (442 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: How to tell a directory from a file? (476 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (445 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (486 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (493 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: How to tell a directory from a file? (552 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (565 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: How to tell a directory from a file? (581 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (599 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: How to tell a directory from a file? (611 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: How to tell a directory from a file? (381 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: How to tell a directory from a file? (626 lines) From: Nat Wooding <nathani@VERIZON.NET> Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Line number in error messages in SAS logLine number in error messages in SAS log (32 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Line number in error messages in SAS log (69 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Line number in error messages in SAS log (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Longitudanal data - How to modify an existing SQL to incorporate one more conditionRe: Longitudanal data - How to modify an existing SQL to incorporate one more condition (162 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Longitudanal data - How to modify an existing SQL to incorporate one more condition (17 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Multilevel Logistic and PrevalenceMultilevel Logistic and Prevalence (52 lines) From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM> Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Need help picking the correct dateNeed help picking the correct date (55 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (101 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (104 lines) From: retired mainframer <retired-mainframer@Q.COM> Re: Need help picking the correct date (122 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (157 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Need help picking the correct date (201 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (218 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (263 lines) From: Dave <david.brewer@UC.EDU> Re: Need help picking the correct date (284 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (292 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Need help picking the correct date (598 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Need help picking the correct date (606 lines) From: Dave <david.brewer@UC.EDU> New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
New Array....?New Array....? (70 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (121 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (133 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (152 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (174 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (198 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (157 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: New Array....? (200 lines) From: Sarah Cox <saslearner2006@GMAIL.COM> Re: New Array....? (117 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: New Array....? (236 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
New Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance LogsNew Blog Post: SAS OLAP Cubes: Automatically Collect ARM Performance Logs (10 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
OT Re: OT: Is OpenClinica Really Slow?OT Re: OT: Is OpenClinica Really Slow? (68 lines) From: Ya Huang <ya.huang@AMYLIN.COM> OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
OT: Is OpenClinica Really Slow?OT: Is OpenClinica Really Slow? (29 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: OT: Is OpenClinica Really Slow? (35 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: OT: Is OpenClinica Really Slow? (54 lines) From: KarlK <karlstudboy@HOTMAIL.COM> OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
OT: Thursday TheoryOT: Thursday Theory (14 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> OT: Thursday Theory (24 lines) From: Ronald Fehd <ron.fehd.macro.maven@GMAIL.COM> Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Oracle vs SAS proc sql "order by"Oracle vs SAS proc sql "order by" (30 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (46 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (54 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (135 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Oracle vs SAS proc sql "order by" (145 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Oracle vs SAS proc sql "order by" (37 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Oracle vs SAS proc sql "order by" (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
PROC SQL: Sum Over All Records and Several VariablesPROC SQL: Sum Over All Records and Several Variables (43 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (73 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: PROC SQL: Sum Over All Records and Several Variables (85 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: PROC SQL: Sum Over All Records and Several Variables (108 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Proc corrProc corr (9 lines) From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU> Re: Proc corr (33 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (212 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> Re: Q: need to nest PDF bookmarks (229 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Q: need to nest PDF bookmarks (22 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
SAS 9.x SubroutinesSAS 9.x Subroutines (18 lines) From: Matt Baker <baker.matthew@BLS.GOV> Re: SAS 9.x Subroutines (40 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS 9.x Subroutines (50 lines) From: Baker, Matthew - BLS <Baker.Matthew@BLS.GOV> Re: SAS 9.x Subroutines (70 lines) From: DUELL, BOB <bd9439@ATT.COM> SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
SAS code for meta analysis.Re: SAS code for meta analysis. (42 lines) From: Steve Denham <stevedrd@YAHOO.COM> SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
SAS guidelines for user blogsSAS guidelines for user blogs (14 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: SAS guidelines for user blogs (26 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: SAS guidelines for user blogs (13 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: SAS guidelines for user blogs (28 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Scoring results from PROC MODECLUSScoring results from PROC MODECLUS (26 lines) From: Peter Mackay <pmackay@WOOLWORTHS.COM.AU> Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Select statement within a DOW LoopSelect statement within a DOW Loop (1874 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1887 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Select statement within a DOW Loop (1869 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Select statement within a DOW Loop (1878 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Re: Select statement within a DOW Loop (1879 lines) From: Dale, Jason - BLS <Dale.Jason@BLS.GOV> Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Statistical Analysis HelpStatistical Analysis Help (16 lines) From: jin li <jinli73@YAHOO.COM> Re: Statistical Analysis Help (46 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
SyncSort vs SAS 9.1.3 and 9.3SyncSort vs SAS 9.1.3 and 9.3 (26 lines) From: Patrice Bourdages <patrice.bourdages@DGAG.CA> Re: SyncSort vs SAS 9.1.3 and 9.3 (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (92 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SyncSort vs SAS 9.1.3 and 9.3 (61 lines) From: William W. Viergever <william@VIERGEVER.NET> Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Transpose data using SQLRe: Transpose data using SQL (53 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (142 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Understanding environment where run_macro executesUnderstanding environment where run_macro executes (133 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (324 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Understanding environment where run_macro executes (510 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (530 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Understanding environment where run_macro executes (562 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (185 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Understanding environment where run_macro executes (102 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Understanding environment where run_macro executes (128 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (192 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (207 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (127 lines) From: Steve Denham <stevedrd@YAHOO.COM> [SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
[SPAM]Re: How to tell a directory from a file?Re: [SPAM]Re: How to tell a directory from a file? (346 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: [SPAM]Re: How to tell a directory from a file? (375 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: [SPAM]Re: How to tell a directory from a file? (453 lines) From: Fried Egg <friedegg2012@GMAIL.COM> better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
better code for customized reporting to text docsbetter code for customized reporting to text docs (161 lines) From: bbser 2009 <bbser2009@GMAIL.COM> chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
chi-square difference test in proc phregchi-square difference test in proc phreg (47 lines) From: Anna Tsui <ascui@UIC.EDU> compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right)compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (61 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (85 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (106 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (134 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (176 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (110 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (202 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (226 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (233 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (95 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (159 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (289 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (93 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (124 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (43 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (48 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (175 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (71 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (181 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (118 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (138 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (157 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (177 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (182 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (228 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (242 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (249 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (235 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (248 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (257 lines) From: dynamicpanel@YAHOO.COM Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (387 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (393 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (422 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (428 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: compressing/left aligning a SAS array (so all non-missing values are on the left, and all missing values are on the right) (462 lines) From: Fried Egg <friedegg2012@GMAIL.COM> counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
counting # of occurrencecounting # of occurrence (22 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: counting # of occurrence (40 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: counting # of occurrence (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
delete format definitiondelete format definition (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: delete format definition (29 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: delete format definition (30 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: delete format definition (23 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: delete format definition (42 lines) From: bbser 2009 <bbser2009@GMAIL.COM> hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
hash table questionhash table question (142 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> Re: hash table question (136 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (178 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: hash table question (213 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: hash table question (107 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: hash table question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: hash table question (18 lines) From: Bin Zhu <bxz01@HEALTH.STATE.NY.US> lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
lost semicolon (Tuesday humor)lost semicolon (Tuesday humor) (32 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
proc format bug?proc format bug? (29 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc format bug? (53 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: proc format bug? (48 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (64 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: proc format bug? (37 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
supported versions of SAS/systemssupported versions of SAS/systems (12 lines) From: F J Kelley <jkelley@UGA.EDU> Re: supported versions of SAS/systems (28 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: supported versions of SAS/systems (55 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: supported versions of SAS/systems (43 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
why lag function does not work in this context?why lag function does not work in this context? (51 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (61 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: why lag function does not work in this context? (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: why lag function does not work in this context? (109 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU>