Automatic reply: SAS-L Digest - 2 Mar 2012 - Special issue (#2012-147)Automatic reply: SAS-L Digest - 2 Mar 2012 - Special issue (#2012-147) (28 lines) From: Gruver, Deena <dgruver@GERON.COM> BUFNO=BUFNO= (26 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: BUFNO= (52 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: BUFNO= (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: BUFNO= (93 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Big Data for the Public Good - Seminar SeriesBig Data for the Public Good - Seminar Series (23 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> Date Format HelpDate Format Help (40 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Re: Date Format Help (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Date Format Help (59 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Date Format Help (42 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Date Format Help (36 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Date Format Help (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Format Help (49 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Discover where those tiny URLs link toDiscover where those tiny URLs link to (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Discover where those tiny URLs link to (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Discover where those tiny URLs link to (48 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Discover where those tiny URLs link to (34 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Example of generating Linear InterpolationExample of generating Linear Interpolation (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Example of generating Linear Interpolation (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Example of generating Linear Interpolation (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (110 lines) From: High, Robin R <rhigh@UNMC.EDU> Re: Example of generating Linear Interpolation (49 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> First. Last.First. Last. (63 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (87 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: First. Last. (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: First. Last. (158 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (109 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Friday HumorRe: Friday Humor (29 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Friday Humor (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Friday Humor (30 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Getting at teradata: ODBC or OLEDB?Getting at teradata: ODBC or OLEDB? (29 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: Getting at teradata: ODBC or OLEDB? (51 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Getting at teradata: ODBC or OLEDB? (40 lines) From: Ari Toikka <toikkari@YAHOO.CO.UK> Help in gplotRe: Help in gplot (17 lines) From: SUBSCRIBE SAS-L Anonymous <rkbattula@DRREDDYS.COM> Re: Help in gplot (50 lines) From: Nat Wooding <nathani@VERIZON.NET> How to add gride lines at summary break using proc reportRe: How to add gride lines at summary break using proc report (168 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
BUFNO=BUFNO= (26 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: BUFNO= (52 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: BUFNO= (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: BUFNO= (93 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Big Data for the Public Good - Seminar SeriesBig Data for the Public Good - Seminar Series (23 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> Date Format HelpDate Format Help (40 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Re: Date Format Help (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Date Format Help (59 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Date Format Help (42 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Date Format Help (36 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Date Format Help (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Format Help (49 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Discover where those tiny URLs link toDiscover where those tiny URLs link to (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Discover where those tiny URLs link to (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Discover where those tiny URLs link to (48 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Discover where those tiny URLs link to (34 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Example of generating Linear InterpolationExample of generating Linear Interpolation (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Example of generating Linear Interpolation (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Example of generating Linear Interpolation (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (110 lines) From: High, Robin R <rhigh@UNMC.EDU> Re: Example of generating Linear Interpolation (49 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> First. Last.First. Last. (63 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (87 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: First. Last. (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: First. Last. (158 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (109 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Friday HumorRe: Friday Humor (29 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Friday Humor (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Friday Humor (30 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Getting at teradata: ODBC or OLEDB?Getting at teradata: ODBC or OLEDB? (29 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: Getting at teradata: ODBC or OLEDB? (51 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Getting at teradata: ODBC or OLEDB? (40 lines) From: Ari Toikka <toikkari@YAHOO.CO.UK> Help in gplotRe: Help in gplot (17 lines) From: SUBSCRIBE SAS-L Anonymous <rkbattula@DRREDDYS.COM> Re: Help in gplot (50 lines) From: Nat Wooding <nathani@VERIZON.NET> How to add gride lines at summary break using proc reportRe: How to add gride lines at summary break using proc report (168 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Big Data for the Public Good - Seminar SeriesBig Data for the Public Good - Seminar Series (23 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> Date Format HelpDate Format Help (40 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Re: Date Format Help (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Date Format Help (59 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Date Format Help (42 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Date Format Help (36 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Date Format Help (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Format Help (49 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Discover where those tiny URLs link toDiscover where those tiny URLs link to (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Discover where those tiny URLs link to (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Discover where those tiny URLs link to (48 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Discover where those tiny URLs link to (34 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Example of generating Linear InterpolationExample of generating Linear Interpolation (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Example of generating Linear Interpolation (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Example of generating Linear Interpolation (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (110 lines) From: High, Robin R <rhigh@UNMC.EDU> Re: Example of generating Linear Interpolation (49 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> First. Last.First. Last. (63 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (87 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: First. Last. (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: First. Last. (158 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (109 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Friday HumorRe: Friday Humor (29 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Friday Humor (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Friday Humor (30 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Getting at teradata: ODBC or OLEDB?Getting at teradata: ODBC or OLEDB? (29 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: Getting at teradata: ODBC or OLEDB? (51 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Getting at teradata: ODBC or OLEDB? (40 lines) From: Ari Toikka <toikkari@YAHOO.CO.UK> Help in gplotRe: Help in gplot (17 lines) From: SUBSCRIBE SAS-L Anonymous <rkbattula@DRREDDYS.COM> Re: Help in gplot (50 lines) From: Nat Wooding <nathani@VERIZON.NET> How to add gride lines at summary break using proc reportRe: How to add gride lines at summary break using proc report (168 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Date Format HelpDate Format Help (40 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Re: Date Format Help (57 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Date Format Help (59 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Date Format Help (42 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Date Format Help (36 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Date Format Help (45 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Format Help (49 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Discover where those tiny URLs link toDiscover where those tiny URLs link to (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Discover where those tiny URLs link to (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Discover where those tiny URLs link to (48 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Discover where those tiny URLs link to (34 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Example of generating Linear InterpolationExample of generating Linear Interpolation (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Example of generating Linear Interpolation (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Example of generating Linear Interpolation (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (110 lines) From: High, Robin R <rhigh@UNMC.EDU> Re: Example of generating Linear Interpolation (49 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> First. Last.First. Last. (63 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (87 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: First. Last. (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: First. Last. (158 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (109 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Friday HumorRe: Friday Humor (29 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Friday Humor (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Friday Humor (30 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Getting at teradata: ODBC or OLEDB?Getting at teradata: ODBC or OLEDB? (29 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: Getting at teradata: ODBC or OLEDB? (51 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Getting at teradata: ODBC or OLEDB? (40 lines) From: Ari Toikka <toikkari@YAHOO.CO.UK> Help in gplotRe: Help in gplot (17 lines) From: SUBSCRIBE SAS-L Anonymous <rkbattula@DRREDDYS.COM> Re: Help in gplot (50 lines) From: Nat Wooding <nathani@VERIZON.NET> How to add gride lines at summary break using proc reportRe: How to add gride lines at summary break using proc report (168 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Discover where those tiny URLs link toDiscover where those tiny URLs link to (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Discover where those tiny URLs link to (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Discover where those tiny URLs link to (48 lines) From: Alan Churchill <savian.net@GMAIL.COM> Re: Discover where those tiny URLs link to (34 lines) From: Gabriel Farkas <g.farkas@GMAIL.COM> Example of generating Linear InterpolationExample of generating Linear Interpolation (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Example of generating Linear Interpolation (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Example of generating Linear Interpolation (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (110 lines) From: High, Robin R <rhigh@UNMC.EDU> Re: Example of generating Linear Interpolation (49 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> First. Last.First. Last. (63 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (87 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: First. Last. (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: First. Last. (158 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (109 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Friday HumorRe: Friday Humor (29 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Friday Humor (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Friday Humor (30 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Getting at teradata: ODBC or OLEDB?Getting at teradata: ODBC or OLEDB? (29 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: Getting at teradata: ODBC or OLEDB? (51 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Getting at teradata: ODBC or OLEDB? (40 lines) From: Ari Toikka <toikkari@YAHOO.CO.UK> Help in gplotRe: Help in gplot (17 lines) From: SUBSCRIBE SAS-L Anonymous <rkbattula@DRREDDYS.COM> Re: Help in gplot (50 lines) From: Nat Wooding <nathani@VERIZON.NET> How to add gride lines at summary break using proc reportRe: How to add gride lines at summary break using proc report (168 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Example of generating Linear InterpolationExample of generating Linear Interpolation (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Example of generating Linear Interpolation (28 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (75 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Example of generating Linear Interpolation (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Example of generating Linear Interpolation (110 lines) From: High, Robin R <rhigh@UNMC.EDU> Re: Example of generating Linear Interpolation (49 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> First. Last.First. Last. (63 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (87 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: First. Last. (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: First. Last. (158 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (109 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Friday HumorRe: Friday Humor (29 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Friday Humor (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Friday Humor (30 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Getting at teradata: ODBC or OLEDB?Getting at teradata: ODBC or OLEDB? (29 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: Getting at teradata: ODBC or OLEDB? (51 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Getting at teradata: ODBC or OLEDB? (40 lines) From: Ari Toikka <toikkari@YAHOO.CO.UK> Help in gplotRe: Help in gplot (17 lines) From: SUBSCRIBE SAS-L Anonymous <rkbattula@DRREDDYS.COM> Re: Help in gplot (50 lines) From: Nat Wooding <nathani@VERIZON.NET> How to add gride lines at summary break using proc reportRe: How to add gride lines at summary break using proc report (168 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
First. Last.First. Last. (63 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (87 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: First. Last. (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: First. Last. (158 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: First. Last. (109 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Friday HumorRe: Friday Humor (29 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Friday Humor (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Friday Humor (30 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Getting at teradata: ODBC or OLEDB?Getting at teradata: ODBC or OLEDB? (29 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: Getting at teradata: ODBC or OLEDB? (51 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Getting at teradata: ODBC or OLEDB? (40 lines) From: Ari Toikka <toikkari@YAHOO.CO.UK> Help in gplotRe: Help in gplot (17 lines) From: SUBSCRIBE SAS-L Anonymous <rkbattula@DRREDDYS.COM> Re: Help in gplot (50 lines) From: Nat Wooding <nathani@VERIZON.NET> How to add gride lines at summary break using proc reportRe: How to add gride lines at summary break using proc report (168 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Friday HumorRe: Friday Humor (29 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Friday Humor (52 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Friday Humor (30 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Getting at teradata: ODBC or OLEDB?Getting at teradata: ODBC or OLEDB? (29 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: Getting at teradata: ODBC or OLEDB? (51 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Getting at teradata: ODBC or OLEDB? (40 lines) From: Ari Toikka <toikkari@YAHOO.CO.UK> Help in gplotRe: Help in gplot (17 lines) From: SUBSCRIBE SAS-L Anonymous <rkbattula@DRREDDYS.COM> Re: Help in gplot (50 lines) From: Nat Wooding <nathani@VERIZON.NET> How to add gride lines at summary break using proc reportRe: How to add gride lines at summary break using proc report (168 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Getting at teradata: ODBC or OLEDB?Getting at teradata: ODBC or OLEDB? (29 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: Getting at teradata: ODBC or OLEDB? (51 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Getting at teradata: ODBC or OLEDB? (40 lines) From: Ari Toikka <toikkari@YAHOO.CO.UK> Help in gplotRe: Help in gplot (17 lines) From: SUBSCRIBE SAS-L Anonymous <rkbattula@DRREDDYS.COM> Re: Help in gplot (50 lines) From: Nat Wooding <nathani@VERIZON.NET> How to add gride lines at summary break using proc reportRe: How to add gride lines at summary break using proc report (168 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Help in gplotRe: Help in gplot (17 lines) From: SUBSCRIBE SAS-L Anonymous <rkbattula@DRREDDYS.COM> Re: Help in gplot (50 lines) From: Nat Wooding <nathani@VERIZON.NET> How to add gride lines at summary break using proc reportRe: How to add gride lines at summary break using proc report (168 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
How to add gride lines at summary break using proc reportRe: How to add gride lines at summary break using proc report (168 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
How to change SAS EG metadata Server nameRe: How to change SAS EG metadata Server name (141 lines) From: Paolo ORIFICI <Orifici@LACAJA.COM.AR> Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Messing upMessing up (289 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (319 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (12 lines) From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK> Messing up (268 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (283 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (60 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (270 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (84 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (90 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: Messing up (104 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (19 lines) From: Ron Wells <Ron.Wells@SLFS.COM> Re: Messing up (301 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (313 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Messing up (328 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (76 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Messing up (87 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (128 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Messing up (142 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Messing up (162 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Messing up (54 lines) From: Nat Wooding <nathani@VERIZON.NET> OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
OT: Friday HumorOT: Friday Humor (13 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> OT: Friday Humor (10 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: OT: Friday Humor (28 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
PROC FREQ for 3 variablesPROC FREQ for 3 variables (25 lines) From: Irin later <irinfigvam@YAHOO.COM> Re: PROC FREQ for 3 variables (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC FREQ for 3 variables (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC FREQ for 3 variables (79 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Panel data analysis random effect and binomial distributionPanel data analysis random effect and binomial distribution (26 lines) From: Shaojie Cui <shaojiec@GMAIL.COM> Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Parsing data from multiple text filesParsing data from multiple text files (51 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (69 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (92 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (165 lines) From: Navi R <navi.mmxi@GMAIL.COM> Re: Parsing data from multiple text files (197 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Parsing data from multiple text files (202 lines) From: Navi R <navi.mmxi@GMAIL.COM> Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Proc Means to Excel File as SheetProc Means to Excel File as Sheet (19 lines) From: Thomas George <tgeorgeturutiyil@GMAIL.COM> Re: Proc Means to Excel File as Sheet (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Means to Excel File as Sheet (17 lines) From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM> Re: Proc Means to Excel File as Sheet (46 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Proc Tabulate Page Dimension dissappears in Enterprise 4.3Proc Tabulate Page Dimension dissappears in Enterprise 4.3 (21 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
RES: Date Format HelpRES: Date Format Help (77 lines) From: Ricardo Gonçalves da Silva <ricardo.gsilva@BANCOVOTORANTIM.COM.BR> Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Replicating PROC SORT NODUPKEY in ***Replicating PROC SORT NODUPKEY in *** (80 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (104 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (153 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (108 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (158 lines) From: KarlK <karlstudboy@HOTMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (193 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Replicating PROC SORT NODUPKEY in *** (51 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (128 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Replicating PROC SORT NODUPKEY in *** (58 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (140 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Replicating PROC SORT NODUPKEY in *** (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Replicating PROC SORT NODUPKEY in *** (174 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (190 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (214 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Replicating PROC SORT NODUPKEY in *** (254 lines) From: Ben Herman <baherman@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (103 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Replicating PROC SORT NODUPKEY in *** (98 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Replicating PROC SORT NODUPKEY in *** (109 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Rolling Sum with uneven intervalsRe: Rolling Sum with uneven intervals (79 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
SAS Analytics 2012 (Cologne, June 2012)SAS Analytics 2012 (Cologne, June 2012) (21 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
SAS Enterprise Miner with OnDemand ProfessionalSAS Enterprise Miner with OnDemand Professional (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
SAS SQL 2: training.SAS SQL 2: training. (24 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
SAS-L Meetup (formerly BOF)SAS-L Meetup (formerly BOF) (19 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfgSASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SASware ballot: provide dialog for changing call to My-Documents in SASv9.cfg (76 lines) From: DUELL, BOB <bd9439@ATT.COM> Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Select top n records in category with otherSelect top n records in category with other (13 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (30 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (41 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (86 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Select top n records in category with other (97 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: Select top n records in category with other (136 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Stripping quotes off of text contained in a macro variableStripping quotes off of text contained in a macro variable (37 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Stripping quotes off of text contained in a macro variable (52 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Stripping quotes off of text contained in a macro variable (55 lines) From: Phil Rack <philrack@MINEQUEST.COM> Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Suggesting improvements in SAS softwareSuggesting improvements in SAS software (26 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Suggesting improvements in SAS software (34 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Suggesting improvements in SAS software (41 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Suggesting improvements in SAS software (54 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Switching from Local PC version of SAS to Server Based version Pros and ConsRe: Switching from Local PC version of SAS to Server Based version Pros and Cons (123 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (157 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (189 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (23 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (95 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (61 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (119 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (125 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (50 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (78 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (96 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (86 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Switching from Local PC version of SAS to Server Based version Pros and Cons (128 lines) From: Ben Powell <bpowell555@GMAIL.COM> System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
System Requirements WizardSystem Requirements Wizard (11 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
System Requirements Wizard - UpdateRe: System Requirements Wizard - Update (19 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Re: System Requirements Wizard - Update (30 lines) From: Jeff Kroll <jeffrey.kroll@US.ING.COM> Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Using IN operator in a macro XXXXUsing IN operator in a macro XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (94 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (121 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using IN operator in a macro XXXX (137 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using IN operator in a macro XXXX (133 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using IN operator in a macro XXXX (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Using IN operator in a macro XXXX (153 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using IN operator in a macro XXXX (145 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Using an AUTOEXEC on a ServerUsing an AUTOEXEC on a Server (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (66 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (73 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using an AUTOEXEC on a Server (90 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (122 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (142 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (167 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Using an AUTOEXEC on a Server (193 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using an AUTOEXEC on a Server (215 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Using the LIKE operator in PROC SQL XXXXUsing the LIKE operator in PROC SQL XXXX (28 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (79 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (47 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (92 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (59 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (67 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (75 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (88 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (115 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: Using the LIKE operator in PROC SQL XXXX (126 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (135 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Using the LIKE operator in PROC SQL XXXX (170 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Using the LIKE operator in PROC SQL XXXX (176 lines) From: Joe Matise <snoopy369@GMAIL.COM> WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
WPS experienceWPS experience (22 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: WPS experience (27 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: WPS experience (38 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXEDRe: Zero-Truncated Binomial Logistic Regression Model Via GLIMMIX and NLMIXED (121 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
about overlay plots in the proc sgplotabout overlay plots in the proc sgplot (21 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (82 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: about overlay plots in the proc sgplot (41 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (91 lines) From: vivian v <v.vivian3@GMAIL.COM> Re: about overlay plots in the proc sgplot (19 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: about overlay plots in the proc sgplot (29 lines) From: vivian v <v.vivian3@GMAIL.COM> automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
automatic array for unique variablesRe: automatic array for unique variables (117 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: automatic array for unique variables (148 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: automatic array for unique variables (161 lines) From: Data _null_; <iebupdte@GMAIL.COM> backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
backup-restorebackup-restore (25 lines) From: Ron Wells <Ron.Wells@SLFS.COM> base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
base sas vs. rbase sas vs. r (24 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (50 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: base sas vs. r (67 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: base sas vs. r (36 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: base sas vs. r (48 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (70 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: base sas vs. r (99 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: base sas vs. r (23 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: base sas vs. r (23 lines) From: .. <ajayohri@YAHOO.COM> Re: base sas vs. r (50 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (123 lines) From: UniQcus <torben.christensen@UNIQCUS.COM> Re: base sas vs. r (122 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (56 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (136 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: base sas vs. r (149 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> Re: base sas vs. r (72 lines) From: oloolo <dynamicpanel@YAHOO.COM> converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
converting text to timeconverting text to time (39 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: converting text to time (56 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: converting text to time (71 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (64 lines) From: Schmid, Dennis (CDC/OSELS/SEPDPO) (CTR) <wfu4@CDC.GOV> Re: converting text to time (59 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: converting text to time (73 lines) From: Burgess, Otto <OBurgess@ATPCO.NET> enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
enhanced editor search/replace vs pretty block commentsenhanced editor search/replace vs pretty block comments (80 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: enhanced editor search/replace vs pretty block comments (87 lines) From: Ben Powell <bpowell555@GMAIL.COM> Re: enhanced editor search/replace vs pretty block comments (103 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
help with creating monthly service utilization datahelp with creating monthly service utilization data (152 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
leading digits in filename: %include Project(03-MyProgram) not workingleading digits in filename: %include Project(03-MyProgram) not working (121 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: leading digits in filename: %include Project(03-MyProgram) not working (138 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (140 lines) From: DUELL, BOB <bd9439@ATT.COM> Re: leading digits in filename: %include Project(03-MyProgram) not working (196 lines) From: DUELL, BOB <bd9439@ATT.COM> linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
linux or solaris sas users in 32 or 64 bit and stattransferlinux or solaris sas users in 32 or 64 bit and stattransfer (44 lines) From: Andre Wielki <wielki@INED.FR> look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
look up: SAS is in the cloudlook up: SAS is in the cloud (24 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
macro questionmacro question (21 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (36 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: macro question (69 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: macro question (90 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: macro question (125 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
ordering one var in proc tabulateordering one var in proc tabulate (27 lines) From: Painter, John (jsp9a) <jsp9a@ESERVICES.VIRGINIA.EDU> Re: ordering one var in proc tabulate (40 lines) From: Joe Matise <snoopy369@GMAIL.COM> output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
output from regression?output from regression? (32 lines) From: Dennis Fisher <Dennis.Fisher@CSULB.EDU> Re: output from regression? (28 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: output from regression? (25 lines) From: Rick Wicklin <rick.wicklin@SAS.COM> Re: output from regression? (53 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: output from regression? (30 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: output from regression? (47 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: output from regression? (12 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
programming questionprogramming question (40 lines) From: satish Kumar <satish.abx@GMAIL.COM> Re: programming question (91 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (63 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (81 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (117 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (74 lines) From: Robin R High <rhigh@UNMC.EDU> Re: programming question (94 lines) From: Zdeb, Michael S <mzdeb@ALBANY.EDU> Re: programming question (115 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: programming question (145 lines) From: Richard Tritz <richardtritz@ATT.NET> Re: programming question (194 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: programming question (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: programming question (111 lines) From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>