ACCESS/Oracle Lots of MessagesRe: ACCESS/Oracle Lots of Messages (73 lines) From: DUELL, BOB <bd9439@ATT.COM> ACCESS/Oracle Lots of Messages (59 lines) From: Alan Churchill <savian.net@GMAIL.COM> Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT StatementRe: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (68 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (38 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (30 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (22 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> An Interesting (I think) PROC MIanalyze QuestionAn Interesting (I think) PROC MIanalyze Question (90 lines) From: Malcolm Jazzbeau <jazzlover111@HOTMAIL.COM> Animated GIF using GREPLAY?Animated GIF using GREPLAY? (35 lines) From: Sadler, John <John.Sadler@ARS.USDA.GOV> Another weird discovery from coding errorRe: Another weird discovery from coding error (38 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Another weird discovery from coding error (24 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: Another weird discovery from coding error (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Another weird discovery from coding error (25 lines) From: DUELL, BOB <bd9439@ATT.COM> Automatic reply: Proc format questionAutomatic reply: Proc format question (14 lines) From: Joe Morrissey <Joe.Morrissey@SAS.COM> Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429)Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429) (15 lines) From: Garabet, Angela <ANGELA.GARABET@LIBERTYMUTUAL.COM> Automatic reply: how to solve this senario?Automatic reply: how to solve this senario? (14 lines) From: Muenchen, Robert A (Bob) <muenchen@UTK.EDU> CodeRe: Code (25 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Code (69 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (33 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Code (46 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Code (13 lines) From: Partha Sinha <pnsinha68@GMAIL.COM> Confidence interval (xbar-2*ybar)Re: Confidence interval (xbar-2*ybar) (28 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (10 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Re: Conidence interval (xbar-2*ybar) (38 lines) From: Steve Denham <stevedrd@YAHOO.COM> Conidence interval (xbar-2*ybar) (17 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT StatementRe: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (68 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (38 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (30 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Advice, Please: INFORMAT Statement in Data Step vs Coding INFORMATS in INPUT Statement (22 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> An Interesting (I think) PROC MIanalyze QuestionAn Interesting (I think) PROC MIanalyze Question (90 lines) From: Malcolm Jazzbeau <jazzlover111@HOTMAIL.COM> Animated GIF using GREPLAY?Animated GIF using GREPLAY? (35 lines) From: Sadler, John <John.Sadler@ARS.USDA.GOV> Another weird discovery from coding errorRe: Another weird discovery from coding error (38 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Another weird discovery from coding error (24 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: Another weird discovery from coding error (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Another weird discovery from coding error (25 lines) From: DUELL, BOB <bd9439@ATT.COM> Automatic reply: Proc format questionAutomatic reply: Proc format question (14 lines) From: Joe Morrissey <Joe.Morrissey@SAS.COM> Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429)Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429) (15 lines) From: Garabet, Angela <ANGELA.GARABET@LIBERTYMUTUAL.COM> Automatic reply: how to solve this senario?Automatic reply: how to solve this senario? (14 lines) From: Muenchen, Robert A (Bob) <muenchen@UTK.EDU> CodeRe: Code (25 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Code (69 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (33 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Code (46 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Code (13 lines) From: Partha Sinha <pnsinha68@GMAIL.COM> Confidence interval (xbar-2*ybar)Re: Confidence interval (xbar-2*ybar) (28 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (10 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Re: Conidence interval (xbar-2*ybar) (38 lines) From: Steve Denham <stevedrd@YAHOO.COM> Conidence interval (xbar-2*ybar) (17 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
An Interesting (I think) PROC MIanalyze QuestionAn Interesting (I think) PROC MIanalyze Question (90 lines) From: Malcolm Jazzbeau <jazzlover111@HOTMAIL.COM> Animated GIF using GREPLAY?Animated GIF using GREPLAY? (35 lines) From: Sadler, John <John.Sadler@ARS.USDA.GOV> Another weird discovery from coding errorRe: Another weird discovery from coding error (38 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Another weird discovery from coding error (24 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: Another weird discovery from coding error (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Another weird discovery from coding error (25 lines) From: DUELL, BOB <bd9439@ATT.COM> Automatic reply: Proc format questionAutomatic reply: Proc format question (14 lines) From: Joe Morrissey <Joe.Morrissey@SAS.COM> Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429)Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429) (15 lines) From: Garabet, Angela <ANGELA.GARABET@LIBERTYMUTUAL.COM> Automatic reply: how to solve this senario?Automatic reply: how to solve this senario? (14 lines) From: Muenchen, Robert A (Bob) <muenchen@UTK.EDU> CodeRe: Code (25 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Code (69 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (33 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Code (46 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Code (13 lines) From: Partha Sinha <pnsinha68@GMAIL.COM> Confidence interval (xbar-2*ybar)Re: Confidence interval (xbar-2*ybar) (28 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (10 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Re: Conidence interval (xbar-2*ybar) (38 lines) From: Steve Denham <stevedrd@YAHOO.COM> Conidence interval (xbar-2*ybar) (17 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Animated GIF using GREPLAY?Animated GIF using GREPLAY? (35 lines) From: Sadler, John <John.Sadler@ARS.USDA.GOV> Another weird discovery from coding errorRe: Another weird discovery from coding error (38 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Another weird discovery from coding error (24 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: Another weird discovery from coding error (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Another weird discovery from coding error (25 lines) From: DUELL, BOB <bd9439@ATT.COM> Automatic reply: Proc format questionAutomatic reply: Proc format question (14 lines) From: Joe Morrissey <Joe.Morrissey@SAS.COM> Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429)Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429) (15 lines) From: Garabet, Angela <ANGELA.GARABET@LIBERTYMUTUAL.COM> Automatic reply: how to solve this senario?Automatic reply: how to solve this senario? (14 lines) From: Muenchen, Robert A (Bob) <muenchen@UTK.EDU> CodeRe: Code (25 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Code (69 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (33 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Code (46 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Code (13 lines) From: Partha Sinha <pnsinha68@GMAIL.COM> Confidence interval (xbar-2*ybar)Re: Confidence interval (xbar-2*ybar) (28 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (10 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Re: Conidence interval (xbar-2*ybar) (38 lines) From: Steve Denham <stevedrd@YAHOO.COM> Conidence interval (xbar-2*ybar) (17 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Another weird discovery from coding errorRe: Another weird discovery from coding error (38 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Another weird discovery from coding error (24 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: Another weird discovery from coding error (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Another weird discovery from coding error (25 lines) From: DUELL, BOB <bd9439@ATT.COM> Automatic reply: Proc format questionAutomatic reply: Proc format question (14 lines) From: Joe Morrissey <Joe.Morrissey@SAS.COM> Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429)Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429) (15 lines) From: Garabet, Angela <ANGELA.GARABET@LIBERTYMUTUAL.COM> Automatic reply: how to solve this senario?Automatic reply: how to solve this senario? (14 lines) From: Muenchen, Robert A (Bob) <muenchen@UTK.EDU> CodeRe: Code (25 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Code (69 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (33 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Code (46 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Code (13 lines) From: Partha Sinha <pnsinha68@GMAIL.COM> Confidence interval (xbar-2*ybar)Re: Confidence interval (xbar-2*ybar) (28 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (10 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Re: Conidence interval (xbar-2*ybar) (38 lines) From: Steve Denham <stevedrd@YAHOO.COM> Conidence interval (xbar-2*ybar) (17 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Automatic reply: Proc format questionAutomatic reply: Proc format question (14 lines) From: Joe Morrissey <Joe.Morrissey@SAS.COM> Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429)Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429) (15 lines) From: Garabet, Angela <ANGELA.GARABET@LIBERTYMUTUAL.COM> Automatic reply: how to solve this senario?Automatic reply: how to solve this senario? (14 lines) From: Muenchen, Robert A (Bob) <muenchen@UTK.EDU> CodeRe: Code (25 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Code (69 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (33 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Code (46 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Code (13 lines) From: Partha Sinha <pnsinha68@GMAIL.COM> Confidence interval (xbar-2*ybar)Re: Confidence interval (xbar-2*ybar) (28 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (10 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Re: Conidence interval (xbar-2*ybar) (38 lines) From: Steve Denham <stevedrd@YAHOO.COM> Conidence interval (xbar-2*ybar) (17 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429)Automatic reply: SAS-L Digest - 12 Jun 2012 - Special issue (#2012-429) (15 lines) From: Garabet, Angela <ANGELA.GARABET@LIBERTYMUTUAL.COM> Automatic reply: how to solve this senario?Automatic reply: how to solve this senario? (14 lines) From: Muenchen, Robert A (Bob) <muenchen@UTK.EDU> CodeRe: Code (25 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Code (69 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (33 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Code (46 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Code (13 lines) From: Partha Sinha <pnsinha68@GMAIL.COM> Confidence interval (xbar-2*ybar)Re: Confidence interval (xbar-2*ybar) (28 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (10 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Re: Conidence interval (xbar-2*ybar) (38 lines) From: Steve Denham <stevedrd@YAHOO.COM> Conidence interval (xbar-2*ybar) (17 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Automatic reply: how to solve this senario?Automatic reply: how to solve this senario? (14 lines) From: Muenchen, Robert A (Bob) <muenchen@UTK.EDU> CodeRe: Code (25 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Code (69 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (33 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Code (46 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Code (13 lines) From: Partha Sinha <pnsinha68@GMAIL.COM> Confidence interval (xbar-2*ybar)Re: Confidence interval (xbar-2*ybar) (28 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (10 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Re: Conidence interval (xbar-2*ybar) (38 lines) From: Steve Denham <stevedrd@YAHOO.COM> Conidence interval (xbar-2*ybar) (17 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
CodeRe: Code (25 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Code (69 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Code (33 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Code (46 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Code (13 lines) From: Partha Sinha <pnsinha68@GMAIL.COM> Confidence interval (xbar-2*ybar)Re: Confidence interval (xbar-2*ybar) (28 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (10 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Re: Conidence interval (xbar-2*ybar) (38 lines) From: Steve Denham <stevedrd@YAHOO.COM> Conidence interval (xbar-2*ybar) (17 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Confidence interval (xbar-2*ybar)Re: Confidence interval (xbar-2*ybar) (28 lines) From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN> Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (10 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Re: Conidence interval (xbar-2*ybar) (38 lines) From: Steve Denham <stevedrd@YAHOO.COM> Conidence interval (xbar-2*ybar) (17 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Conidence interval (xbar-2*ybar)Re: Conidence interval (xbar-2*ybar) (10 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> Re: Conidence interval (xbar-2*ybar) (38 lines) From: Steve Denham <stevedrd@YAHOO.COM> Conidence interval (xbar-2*ybar) (17 lines) From: SUBSCRIBE SAS-L krishna <rkbattula@DRREDDYS.COM> ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
ConnectionsRe: Connections (29 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Connections (23 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Creating Folder Dynamically in SASRe: Creating Folder Dynamically in SAS (23 lines) From: Michelle Zunnurain <mzunnurain@HDMS.COM> Re: Creating Folder Dynamically in SAS (102 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Creating Folder Dynamically in SAS (79 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Creating Folder Dynamically in SAS (64 lines) From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM> Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Datastep memory leak?Re: Datastep memory leak? (286 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (224 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (127 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (422 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (431 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Datastep memory leak? (390 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Datastep memory leak? (345 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Dates when extracting data from SQL server with PROC SQLRe: Dates when extracting data from SQL server with PROC SQL (96 lines) From: Joe Matise <snoopy369@GMAIL.COM> Dates when extracting data from SQL server with PROC SQL (59 lines) From: Howard Alper <halper@HEALTH.NYC.GOV> Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Graphing GLM Regression Equation Against Dummy ValuesRe: Graphing GLM Regression Equation Against Dummy Values (121 lines) From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU> Re: Graphing GLM Regression Equation Against Dummy Values (104 lines) From: Randi Black <randiblack@GMAIL.COM> Re: Graphing GLM Regression Equation Against Dummy Values (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Graphing GLM Regression Equation Against Dummy Values (44 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (29 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Graphing GLM Regression Equation Against Dummy Values (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Graphing GLM Regression Equation Against Dummy Values (23 lines) From: Randi Black <randiblack@GMAIL.COM> Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Howto Fix a dead SAS LogRe: Howto Fix a dead SAS Log (54 lines) From: Ben Powell <bpowell555@GMAIL.COM> Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Importing Excel with Text content - Import.IO errorImporting Excel with Text content - Import.IO error (15 lines) From: Rob Hudson <caveatrob@GMAIL.COM> In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
In() FunctionRe: In() Function (86 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Re: In() Function (266 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: In() Function (268 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (214 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: In() Function (168 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: In() Function (166 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (135 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> In() Function (11 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (60 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: In() Function (228 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (193 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (175 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (142 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: In() Function (127 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (109 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: In() Function (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (56 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: In() Function (51 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: In() Function (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> In() Function (7 lines) From: Titaan Titaan <titaan08@GMAIL.COM> Re: In() Function (141 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: In() Function (120 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: In() Function (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: In() Function (75 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> In() Function (44 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Longitudanal data - How to modify an existing SQL to incorporate one more conditionLongitudanal data - How to modify an existing SQL to incorporate one more condition (141 lines) From: Mirisage Fernando <neilfrnnd@GMAIL.COM> New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
New Leadership Council for the SAS CommunityRe: New Leadership Council for the SAS Community (76 lines) From: Joseph Kelley <jkelley@UGA.EDU> Re: New Leadership Council for the SAS Community (89 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (89 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: New Leadership Council for the SAS Community (77 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (66 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (44 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: New Leadership Council for the SAS Community (149 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: New Leadership Council for the SAS Community (104 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (155 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: New Leadership Council for the SAS Community (214 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: New Leadership Council for the SAS Community (74 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: New Leadership Council for the SAS Community (91 lines) From: .. <ajayohri@YAHOO.COM> Re: New Leadership Council for the SAS Community (84 lines) From: Arthur Tabachneck <art297@ROGERS.COM> New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
New Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User StorageNew Post BI-NOTES: SAS Enterprise Guide: Best Practice for Centralized User Storage (18 lines) From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM> New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
New trojan going aroundNew trojan going around (12 lines) From: Arthur Tabachneck <art297@ROGERS.COM> PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
PROC MIanalyze and Descriptive Statistics QuestionPROC MIanalyze and Descriptive Statistics Question (91 lines) From: Greenbaum, Mark A. <Mark.Greenbaum@VA.GOV> Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Proc Tabulate questionRe: Proc Tabulate question (12 lines) From: Wendi Wright <wendi_wright@CTB.COM> Re: Proc Tabulate question (57 lines) From: Wright, Wendi <Wendi_Wright@CTB.COM> Re: Proc Tabulate question (36 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Proc Tabulate question (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc Tabulate question (23 lines) From: Wendi Wright <wendi_wright@CTB.COM> Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Proc format questionRe: Proc format question (102 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (88 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Proc format question (64 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Proc format question (152 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (141 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Proc format question (134 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (111 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Proc format question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Proc format question (73 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc format question (59 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Proc format question (49 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV> Proc format question (28 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Programmtically accessing WRS ReportsRe: Programmtically accessing WRS Reports (55 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Re: Programmtically accessing WRS Reports (65 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Programmtically accessing WRS Reports (50 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Programmtically accessing WRS Reports (38 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Programmtically accessing WRS Reports (21 lines) From: Allen Ziegenfus <a.ziegenfus@ANAXIMA.COM> Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Q: need to nest PDF bookmarksRe: Q: need to nest PDF bookmarks (112 lines) From: Roland Berry <rolandberry@HOTMAIL.COM> SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
SQL questionRe: SQL question (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL question (18 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL question (13 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
SQL: joining on closest datetime matchRe: SQL: joining on closest datetime match (751 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (712 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (633 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (64 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (636 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (447 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (178 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (258 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (249 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (507 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: SQL: joining on closest datetime match (215 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: SQL: joining on closest datetime match (179 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (164 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (133 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL: joining on closest datetime match (97 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: SQL: joining on closest datetime match (60 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SQL: joining on closest datetime match (93 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL: joining on closest datetime match (63 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: SQL: joining on closest datetime match (79 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SQL: joining on closest datetime match (44 lines) From: oloolo <dynamicpanel@YAHOO.COM> SQL: joining on closest datetime match (37 lines) From: Kathleen Askland <k.askland@GMAIL.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Statistical Analysis of Demographics of Current Leadership Council for the SAS CommunityRe: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (244 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (16 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (25 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (169 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (24 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (150 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (124 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (85 lines) From: William W. Viergever <william@VIERGEVER.NET> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (18 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (46 lines) From: .. <ajayohri@YAHOO.COM> Re: Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (17 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Statistical Analysis of Demographics of Current Leadership Council for the SAS Community (57 lines) From: .. <ajayohri@YAHOO.COM> Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Transpose data using SQLRe: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (83 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (21 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (66 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (51 lines) From: Sigurd W. Hermansen <hermans1@WESTAT.COM> Re: Transpose data using SQL (39 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (32 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: Transpose data using SQL (104 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Transpose data using SQL (24 lines) From: Fried Egg <friedegg2012@GMAIL.COM> Re: Transpose data using SQL (14 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (175 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (28 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (9 lines) From: Joseph Hinson <jwhinson@GMAIL.COM> Re: Transpose data using SQL (167 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (154 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (24 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: Transpose data using SQL (136 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Transpose data using SQL (108 lines) From: Ben <benpub7@YAHOO.COM> Re: Transpose data using SQL (98 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Transpose data using SQL (39 lines) From: Ben <benpub7@YAHOO.COM> Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
Weighting Scheme in GLIMMIX?Re: Weighting Scheme in GLIMMIX? (105 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Weighting Scheme in GLIMMIX? (143 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: Weighting Scheme in GLIMMIX? (127 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Weighting Scheme in GLIMMIX? (45 lines) From: Steve Denham <stevedrd@YAHOO.COM> Weighting Scheme in GLIMMIX? (37 lines) From: R B <ryan.andrew.black@GMAIL.COM> autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
autoexec insert or append in 9.3 new optionRe: autoexec insert or append in 9.3 new option (54 lines) From: Fehd, Ronald J. (CDC/OCOO/OCIO/ITSO) <rjf2@CDC.GOV> Re: autoexec insert or append in 9.3 new option (37 lines) From: Andre Wielki <wielki@INED.FR> autoexec insert or append in 9.3 new option (28 lines) From: Andre Wielki <wielki@INED.FR> do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
do not compute percent in proc freq out= data setRe: do not compute percent in proc freq out= data set (146 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (129 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: do not compute percent in proc freq out= data set (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: do not compute percent in proc freq out= data set (108 lines) From: Fried Egg <friedegg2012@GMAIL.COM> drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
drawing a line representing a median on a bar chartRe: drawing a line representing a median on a bar chart (61 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: drawing a line representing a median on a bar chart (26 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> drawing a line representing a median on a bar chart (29 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
font in data _NULL_Re: font in data _NULL_ (53 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> font in data _NULL_ (30 lines) From: sm dong <sasdong18@GMAIL.COM> how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
how to hash-object this?Re: how to hash-object this? (116 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (151 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (139 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: how to hash-object this? (136 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: how to hash-object this? (116 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
how to solve this senario?Re: how to solve this senario? (22 lines) From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM> Re: how to solve this senario? (98 lines) From: Nat Wooding <nathani@VERIZON.NET> how to solve this senario? (51 lines) From: Nway <hymadsk@GMAIL.COM> joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
joining on closest datetime matchRe: joining on closest datetime match (73 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: joining on closest datetime match (84 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>
simple datalines questionRe: simple datalines question (64 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: simple datalines question (83 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: simple datalines question (52 lines) From: Data _null_; <iebupdte@GMAIL.COM> simple datalines question (28 lines) From: adel F. <adel_tangi@YAHOO.FR>