10^9/L becomes 10/L when sent to Excel from SAS via ExcelXP tagset, why?10^9/L becomes 10/L when sent to Excel from SAS via ExcelXP tagset, why? (18 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: 10^9/L becomes 10/L when sent to Excel from SAS via ExcelXP tagset, why? (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: 10^9/L becomes 10/L when sent to Excel from SAS via ExcelXP tagset, why? (12 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> <No subject><No subject> (12 lines) From: Ed Hartig <hartig4@SBCGLOBAL.NET> <No subject> (13 lines) From: Daniel Reyes <junkdalejreyes@YAHOO.COM> ASCII text into unique numeric:Re: ASCII text into unique numeric: (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ASCII text into unique numeric: (20 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Automatic reply: SAS-L Digest - 10 Jul 2011 to 11 Jul 2011 - Special issue (#2011-666)Automatic reply: SAS-L Digest - 10 Jul 2011 to 11 Jul 2011 - Special issue (#2011-666) (16 lines) From: ROMOLINI, VALERIO <valerio.romolini@NOVARTIS.COM> Automatic reply: SAS-L Digest - 11 Jul 2011 - Special issue (#2011-667)Automatic reply: SAS-L Digest - 11 Jul 2011 - Special issue (#2011-667) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Call Execure with dataset values as macro parameter inputsCall Execure with dataset values as macro parameter inputs (32 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (73 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Call Execure with dataset values as macro parameter inputs (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (20 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (47 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Call Execure with dataset values as macro parameter inputs (66 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Call Execure with dataset values as macro parameter inputs (86 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Call Execure with dataset values as macro parameter inputs (13 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email?Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (17 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (20 lines) From: Joe Kelley <jkelley@UGA.EDU> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (21 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (16 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (63 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Chance to Make SAS-L History: Did You Know That... (35 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Chance to Make SAS-L History: Did You Know That... (28 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (61 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Charting a New Course with SAS 9.3 SAS/Graph!Charting a New Course with SAS 9.3 SAS/Graph! (61 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Ryan Boyle <ryanjames@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (68 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> DF in nested GLIMMIX modelDF in nested GLIMMIX model (66 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Re: DF in nested GLIMMIX model (109 lines) From: Robin R High <rhigh@UNMC.EDU> Re: DF in nested GLIMMIX model (14 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Day of Year functionDay of Year function (27 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (48 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Day of Year function (39 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Day of Year function (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Day of Year function (117 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (65 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Day of Year function (100 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (133 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (176 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
<No subject><No subject> (12 lines) From: Ed Hartig <hartig4@SBCGLOBAL.NET> <No subject> (13 lines) From: Daniel Reyes <junkdalejreyes@YAHOO.COM> ASCII text into unique numeric:Re: ASCII text into unique numeric: (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ASCII text into unique numeric: (20 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Automatic reply: SAS-L Digest - 10 Jul 2011 to 11 Jul 2011 - Special issue (#2011-666)Automatic reply: SAS-L Digest - 10 Jul 2011 to 11 Jul 2011 - Special issue (#2011-666) (16 lines) From: ROMOLINI, VALERIO <valerio.romolini@NOVARTIS.COM> Automatic reply: SAS-L Digest - 11 Jul 2011 - Special issue (#2011-667)Automatic reply: SAS-L Digest - 11 Jul 2011 - Special issue (#2011-667) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Call Execure with dataset values as macro parameter inputsCall Execure with dataset values as macro parameter inputs (32 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (73 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Call Execure with dataset values as macro parameter inputs (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (20 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (47 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Call Execure with dataset values as macro parameter inputs (66 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Call Execure with dataset values as macro parameter inputs (86 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Call Execure with dataset values as macro parameter inputs (13 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email?Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (17 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (20 lines) From: Joe Kelley <jkelley@UGA.EDU> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (21 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (16 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (63 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Chance to Make SAS-L History: Did You Know That... (35 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Chance to Make SAS-L History: Did You Know That... (28 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (61 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Charting a New Course with SAS 9.3 SAS/Graph!Charting a New Course with SAS 9.3 SAS/Graph! (61 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Ryan Boyle <ryanjames@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (68 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> DF in nested GLIMMIX modelDF in nested GLIMMIX model (66 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Re: DF in nested GLIMMIX model (109 lines) From: Robin R High <rhigh@UNMC.EDU> Re: DF in nested GLIMMIX model (14 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Day of Year functionDay of Year function (27 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (48 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Day of Year function (39 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Day of Year function (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Day of Year function (117 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (65 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Day of Year function (100 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (133 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (176 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
ASCII text into unique numeric:Re: ASCII text into unique numeric: (70 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: ASCII text into unique numeric: (20 lines) From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV> Automatic reply: SAS-L Digest - 10 Jul 2011 to 11 Jul 2011 - Special issue (#2011-666)Automatic reply: SAS-L Digest - 10 Jul 2011 to 11 Jul 2011 - Special issue (#2011-666) (16 lines) From: ROMOLINI, VALERIO <valerio.romolini@NOVARTIS.COM> Automatic reply: SAS-L Digest - 11 Jul 2011 - Special issue (#2011-667)Automatic reply: SAS-L Digest - 11 Jul 2011 - Special issue (#2011-667) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Call Execure with dataset values as macro parameter inputsCall Execure with dataset values as macro parameter inputs (32 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (73 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Call Execure with dataset values as macro parameter inputs (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (20 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (47 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Call Execure with dataset values as macro parameter inputs (66 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Call Execure with dataset values as macro parameter inputs (86 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Call Execure with dataset values as macro parameter inputs (13 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email?Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (17 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (20 lines) From: Joe Kelley <jkelley@UGA.EDU> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (21 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (16 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (63 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Chance to Make SAS-L History: Did You Know That... (35 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Chance to Make SAS-L History: Did You Know That... (28 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (61 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Charting a New Course with SAS 9.3 SAS/Graph!Charting a New Course with SAS 9.3 SAS/Graph! (61 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Ryan Boyle <ryanjames@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (68 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> DF in nested GLIMMIX modelDF in nested GLIMMIX model (66 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Re: DF in nested GLIMMIX model (109 lines) From: Robin R High <rhigh@UNMC.EDU> Re: DF in nested GLIMMIX model (14 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Day of Year functionDay of Year function (27 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (48 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Day of Year function (39 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Day of Year function (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Day of Year function (117 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (65 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Day of Year function (100 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (133 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (176 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Automatic reply: SAS-L Digest - 10 Jul 2011 to 11 Jul 2011 - Special issue (#2011-666)Automatic reply: SAS-L Digest - 10 Jul 2011 to 11 Jul 2011 - Special issue (#2011-666) (16 lines) From: ROMOLINI, VALERIO <valerio.romolini@NOVARTIS.COM> Automatic reply: SAS-L Digest - 11 Jul 2011 - Special issue (#2011-667)Automatic reply: SAS-L Digest - 11 Jul 2011 - Special issue (#2011-667) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Call Execure with dataset values as macro parameter inputsCall Execure with dataset values as macro parameter inputs (32 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (73 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Call Execure with dataset values as macro parameter inputs (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (20 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (47 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Call Execure with dataset values as macro parameter inputs (66 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Call Execure with dataset values as macro parameter inputs (86 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Call Execure with dataset values as macro parameter inputs (13 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email?Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (17 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (20 lines) From: Joe Kelley <jkelley@UGA.EDU> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (21 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (16 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (63 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Chance to Make SAS-L History: Did You Know That... (35 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Chance to Make SAS-L History: Did You Know That... (28 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (61 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Charting a New Course with SAS 9.3 SAS/Graph!Charting a New Course with SAS 9.3 SAS/Graph! (61 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Ryan Boyle <ryanjames@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (68 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> DF in nested GLIMMIX modelDF in nested GLIMMIX model (66 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Re: DF in nested GLIMMIX model (109 lines) From: Robin R High <rhigh@UNMC.EDU> Re: DF in nested GLIMMIX model (14 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Day of Year functionDay of Year function (27 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (48 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Day of Year function (39 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Day of Year function (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Day of Year function (117 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (65 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Day of Year function (100 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (133 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (176 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Automatic reply: SAS-L Digest - 11 Jul 2011 - Special issue (#2011-667)Automatic reply: SAS-L Digest - 11 Jul 2011 - Special issue (#2011-667) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Call Execure with dataset values as macro parameter inputsCall Execure with dataset values as macro parameter inputs (32 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (73 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Call Execure with dataset values as macro parameter inputs (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (20 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (47 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Call Execure with dataset values as macro parameter inputs (66 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Call Execure with dataset values as macro parameter inputs (86 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Call Execure with dataset values as macro parameter inputs (13 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email?Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (17 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (20 lines) From: Joe Kelley <jkelley@UGA.EDU> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (21 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (16 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (63 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Chance to Make SAS-L History: Did You Know That... (35 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Chance to Make SAS-L History: Did You Know That... (28 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (61 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Charting a New Course with SAS 9.3 SAS/Graph!Charting a New Course with SAS 9.3 SAS/Graph! (61 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Ryan Boyle <ryanjames@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (68 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> DF in nested GLIMMIX modelDF in nested GLIMMIX model (66 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Re: DF in nested GLIMMIX model (109 lines) From: Robin R High <rhigh@UNMC.EDU> Re: DF in nested GLIMMIX model (14 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Day of Year functionDay of Year function (27 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (48 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Day of Year function (39 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Day of Year function (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Day of Year function (117 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (65 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Day of Year function (100 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (133 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (176 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Call Execure with dataset values as macro parameter inputsCall Execure with dataset values as macro parameter inputs (32 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (73 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Call Execure with dataset values as macro parameter inputs (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (20 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Call Execure with dataset values as macro parameter inputs (47 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Call Execure with dataset values as macro parameter inputs (66 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Call Execure with dataset values as macro parameter inputs (86 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Call Execure with dataset values as macro parameter inputs (13 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email?Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (17 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (20 lines) From: Joe Kelley <jkelley@UGA.EDU> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (21 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (16 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (63 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Chance to Make SAS-L History: Did You Know That... (35 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Chance to Make SAS-L History: Did You Know That... (28 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (61 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Charting a New Course with SAS 9.3 SAS/Graph!Charting a New Course with SAS 9.3 SAS/Graph! (61 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Ryan Boyle <ryanjames@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (68 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> DF in nested GLIMMIX modelDF in nested GLIMMIX model (66 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Re: DF in nested GLIMMIX model (109 lines) From: Robin R High <rhigh@UNMC.EDU> Re: DF in nested GLIMMIX model (14 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Day of Year functionDay of Year function (27 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (48 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Day of Year function (39 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Day of Year function (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Day of Year function (117 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (65 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Day of Year function (100 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (133 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (176 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email?Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (17 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (20 lines) From: Joe Kelley <jkelley@UGA.EDU> Re: Can't post/response from http://listserv.uga.edu/archives/sas-l.html, but OK from email? (21 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (16 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (63 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Chance to Make SAS-L History: Did You Know That... (35 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Chance to Make SAS-L History: Did You Know That... (28 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (61 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Charting a New Course with SAS 9.3 SAS/Graph!Charting a New Course with SAS 9.3 SAS/Graph! (61 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Ryan Boyle <ryanjames@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (68 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> DF in nested GLIMMIX modelDF in nested GLIMMIX model (66 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Re: DF in nested GLIMMIX model (109 lines) From: Robin R High <rhigh@UNMC.EDU> Re: DF in nested GLIMMIX model (14 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Day of Year functionDay of Year function (27 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (48 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Day of Year function (39 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Day of Year function (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Day of Year function (117 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (65 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Day of Year function (100 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (133 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (176 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (16 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (63 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Chance to Make SAS-L History: Did You Know That... (35 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Chance to Make SAS-L History: Did You Know That... (28 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Chance to Make SAS-L History: Did You Know That... (61 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Charting a New Course with SAS 9.3 SAS/Graph!Charting a New Course with SAS 9.3 SAS/Graph! (61 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Ryan Boyle <ryanjames@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (68 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> DF in nested GLIMMIX modelDF in nested GLIMMIX model (66 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Re: DF in nested GLIMMIX model (109 lines) From: Robin R High <rhigh@UNMC.EDU> Re: DF in nested GLIMMIX model (14 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Day of Year functionDay of Year function (27 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (48 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Day of Year function (39 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Day of Year function (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Day of Year function (117 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (65 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Day of Year function (100 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (133 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (176 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Charting a New Course with SAS 9.3 SAS/Graph!Charting a New Course with SAS 9.3 SAS/Graph! (61 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Ryan Boyle <ryanjames@GMAIL.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (68 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Charting a New Course with SAS 9.3 SAS/Graph! (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> DF in nested GLIMMIX modelDF in nested GLIMMIX model (66 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Re: DF in nested GLIMMIX model (109 lines) From: Robin R High <rhigh@UNMC.EDU> Re: DF in nested GLIMMIX model (14 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Day of Year functionDay of Year function (27 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (48 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Day of Year function (39 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Day of Year function (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Day of Year function (117 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (65 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Day of Year function (100 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (133 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (176 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
DF in nested GLIMMIX modelDF in nested GLIMMIX model (66 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Re: DF in nested GLIMMIX model (109 lines) From: Robin R High <rhigh@UNMC.EDU> Re: DF in nested GLIMMIX model (14 lines) From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE> Day of Year functionDay of Year function (27 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (48 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Day of Year function (39 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Day of Year function (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Day of Year function (117 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (65 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Day of Year function (100 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (133 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (176 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Day of Year functionDay of Year function (27 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (48 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Day of Year function (39 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Day of Year function (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Day of Year function (117 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (65 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Day of Year function (100 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Day of Year function (133 lines) From: Joe DeShon <joedeshon@COMCAST.NET> Re: Day of Year function (176 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
ESTIMATE statement in NLMIXEDESTIMATE statement in NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
ExcelXP and blank cellsExcelXP and blank cells (17 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: ExcelXP and blank cells (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
ExcelXP by group processing has unexpected blank lineRe: ExcelXP by group processing has unexpected blank line (18 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
ExcelXP embedded titles and footnotesExcelXP embedded titles and footnotes (52 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: ExcelXP embedded titles and footnotes (78 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: ExcelXP embedded titles and footnotes (63 lines) From: Joe Matise <snoopy369@GMAIL.COM> ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
ExcelXp and blank cellsRe: ExcelXp and blank cells (59 lines) From: Andre Wielki <wielki@INED.FR> Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formatsExporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (66 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Exporting@newdonner.dartmouth.edu SAS data with Formats into excel keeping the formats (106 lines) From: Nat Wooding <nathani@VERIZON.NET> FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
FDA clinical trials: SOP for access a databaseFDA clinical trials: SOP for access a database (49 lines) From: Viel, Kevin <kviel@SJHA.ORG> Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Help counting eventsHelp counting events (77 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (7 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> Re: Help counting events (91 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Help counting events (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Help counting events (91 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Help counting events (119 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: Help counting events (18 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (71 lines) From: Ben <benpub7@YAHOO.COM> Re: Help counting events (9 lines) From: Cynthia qiu <cynqiu@YAHOO.COM> How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
How to "decode" these values for _atopcode_ from audit trialsHow to "decode" these values for _atopcode_ from audit trials (23 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: How to "decode" these values for _atopcode_ from audit trials (60 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Import Local SAS FileImport Local SAS File (34 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Is SAS corrupted?Is SAS corrupted? (35 lines) From: Lacey, Linda M <laceyl@MUSC.EDU> Re: Is SAS corrupted? (55 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (79 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: Is SAS corrupted? (101 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Is SAS corrupted? (108 lines) From: Data _null_; <iebupdte@GMAIL.COM> It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course!It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (41 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (66 lines) From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (31 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (70 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (92 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (97 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: It's Heeeeerrrrreeeee! SAS 9.2 + .1 = ... SAS 9.3, of Course! (109 lines) From: Arthur Tabachneck <art297@ROGERS.COM> It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
It's Nice to See SAS Nine-Point-Three!It's Nice to See SAS Nine-Point-Three! (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (64 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: It's Nice to See SAS Nine-Point-Three! (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (79 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: It's Nice to See SAS Nine-Point-Three! (62 lines) From: Viel, Kevin <kviel@SJHA.ORG> Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Keeping the decimalKeeping the decimal (19 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: Keeping the decimal (45 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Keeping the decimal (32 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Keeping the decimal (37 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
LaTeX for a NESUG or SGF poster?LaTeX for a NESUG or SGF poster? (28 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LaTeX for a NESUG or SGF poster? (38 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: LaTeX for a NESUG or SGF poster? (48 lines) From: Murphy Choy <goladin@GMAIL.COM> LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
LibName ODBC: MySQLLibName ODBC: MySQL (46 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (49 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (88 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: LibName ODBC: MySQL (103 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: LibName ODBC: MySQL (11 lines) From: Byron Kirby <byronkirby@GMAIL.COM> Re: LibName ODBC: MySQL (142 lines) From: Viel, Kevin <kviel@SJHA.ORG> Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Looking for ExcelXP featureRe: Looking for ExcelXP feature (29 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Multi-tabbed Excel SpreadsheetsMulti-tabbed Excel Spreadsheets (40 lines) From: Kroll, J. (Jeffrey) <Jeffrey.Kroll@US.ING.COM> Re: Multi-tabbed Excel Spreadsheets (45 lines) From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US> Re: Multi-tabbed Excel Spreadsheets (53 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Multi-tabbed Excel Spreadsheets (61 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Multi-tabbed Excel Spreadsheets (114 lines) From: Data _null_; <iebupdte@GMAIL.COM> OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
OT: QingDaoOT: QingDao (50 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
OT: anyone using Nvivo?OT: anyone using Nvivo? (18 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
On-line, hands-on, SAS Training: August & Sept. 2011On-line, hands-on, SAS Training: August & Sept. 2011 (48 lines) From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM> PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
PHREG for conditional logistic regressionPHREG for conditional logistic regression (28 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (86 lines) From: Robin R High <rhigh@UNMC.EDU> Re: PHREG for conditional logistic regression (91 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> Re: PHREG for conditional logistic regression (98 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PHREG for conditional logistic regression (114 lines) From: Jill Stoltzfus <jillstol@YAHOO.COM> PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
PROC LOGISTIC OutputPROC LOGISTIC Output (55 lines) From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR> Re: PROC LOGISTIC Output (55 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Proc Lifetest - Survival Graph Patients At RiskProc Lifetest - Survival Graph Patients At Risk (37 lines) From: RK <ryan.krause@GMAIL.COM> Re: Proc Lifetest - Survival Graph Patients At Risk (39 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Proc sort vs. Proc SQL; order byProc sort vs. Proc SQL; order by (33 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Proceedings from PharmaSUGRe: Proceedings from PharmaSUG (171 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Proceedings from PharmaSUG (48 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: Proceedings from PharmaSUG (95 lines) From: Viel, Kevin <kviel@SJHA.ORG> QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
QingDaoRe: QingDao (64 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Question about how to analyze repeated measures QOL data with attritionQuestion about how to analyze repeated measures QOL data with attrition (47 lines) From: Paul Miller <pjmiller_57@YAHOO.COM> Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Read in an entire line of raw data including the leading spacesRead in an entire line of raw data including the leading spaces (19 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (96 lines) From: John Smith <js8765@GOOGLEMAIL.COM> Re: Read in an entire line of raw data including the leading spaces (93 lines) From: Viel, Kevin <kviel@SJHA.ORG> Re: Read in an entire line of raw data including the leading spaces (140 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Read in an entire line of raw data including the leading spaces (112 lines) From: Joe Matise <snoopy369@GMAIL.COM> Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Repeated measures: complex issuesRepeated measures: complex issues (45 lines) From: Viel, Kevin <kviel@SJHA.ORG> Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Reporting UNIVARIATE resultsReporting UNIVARIATE results (106 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> Re: Reporting UNIVARIATE results (174 lines) From: Data _null_; <iebupdte@GMAIL.COM> SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
SAS 9.3 notesRe: SAS 9.3 notes (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3 notes (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
SAS 9.3?Re: SAS 9.3? (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
SAS EG Project - Making Global ChangesSAS EG Project - Making Global Changes (44 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Re: SAS EG Project - Making Global Changes (63 lines) From: Sterling Paramore <gnilrets@GMAIL.COM> SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
SET, MODIFY / KEY=, consecutive duplicatesSET, MODIFY / KEY=, consecutive duplicates (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SET, MODIFY / KEY=, consecutive duplicates (107 lines) From: oloolo <dynamicpanel@YAHOO.COM> Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Standard errors of marginal effects in LOGISTICStandard errors of marginal effects in LOGISTIC (123 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Standard errors of marginal effects in LOGISTIC (39 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: Standard errors of marginal effects in LOGISTIC (152 lines) From: Reitz, Stuart <Stuart.Reitz@ARS.USDA.GOV> Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Successor to Learning EditionSuccessor to Learning Edition (75 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (86 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: Successor to Learning Edition (82 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Successor to Learning Edition (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> Re: Successor to Learning Edition (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Tolerance option in proc glm -- interaction -> dummy001?Tolerance option in proc glm -- interaction -> dummy001? (45 lines) From: Erin McMullen Jonaitis <jonaitis@WISC.EDU> Re: Tolerance option in proc glm -- interaction -> dummy001? (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
Uploading XLS files to UNIXRe: Uploading XLS files to UNIX (31 lines) From: Paulo Rodrigo <rodrigo_paulo@YAHOO.COM.BR> add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
add single quotation in a charactor valueadd single quotation in a charactor value (14 lines) From: df ss <tggsun@YAHOO.COM> Re: add single quotation in a charactor value (40 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
alpha-numeric data split into two tables?Re: alpha-numeric data split into two tables? (34 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (13 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (76 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: alpha-numeric data split into two tables? (45 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (22 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: alpha-numeric data split into two tables? (43 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: alpha-numeric data split into two tables? (56 lines) From: Nat Wooding <nathani@VERIZON.NET> blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
blank ???Re: blank ??? (105 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
create dummy variables for bivariate analysescreate dummy variables for bivariate analyses (21 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (65 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: create dummy variables for bivariate analyses (30 lines) From: oslo <hokut1@YAHOO.COM> Re: create dummy variables for bivariate analyses (18 lines) From: byron kirby <byronkirby@GMAIL.COM> Re: create dummy variables for bivariate analyses (36 lines) From: oslo <hokut1@YAHOO.COM> length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
length= in sql pass through to oraclelength= in sql pass through to oracle (37 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (53 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (69 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (76 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: length= in sql pass through to oracle (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: length= in sql pass through to oracle (117 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (171 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: length= in sql pass through to oracle (204 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: length= in sql pass through to oracle (224 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: length= in sql pass through to oracle (182 lines) From: Mary <mlhoward@AVALON.NET> Re: length= in sql pass through to oracle (206 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
nvivoRe: nvivo (32 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
odd macro variable behavior SYS_SQL_IP_ALLodd macro variable behavior SYS_SQL_IP_ALL (95 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: odd macro variable behavior SYS_SQL_IP_ALL (46 lines) From: Richard Devenezia <rdevenezia@GMAIL.COM> proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
proc sql flow=n m;proc sql flow=n m; (19 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: proc sql flow=n m; (66 lines) From: bbser 2009 <bbser2009@GMAIL.COM> test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
test post to SAS-Ltest post to SAS-L (8 lines) From: Joe Kelley <jkelley@UGA.EDU> test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
test, please ignoretest, please ignore (11 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: test, please ignore (26 lines) From: Murphy Choy <goladin@GMAIL.COM> transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
transcoding warning while reading a flatfile in DI-StudioRe: transcoding warning while reading a flatfile in DI-Studio (95 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (89 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: transcoding warning while reading a flatfile in DI-Studio (124 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: transcoding warning while reading a flatfile in DI-Studio (148 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
two questions: special character and latextwo questions: special character and latex (12 lines) From: Huaandrew <andrew0845@HOTMAIL.COM> Re: two questions: special character and latex (30 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: two questions: special character and latex (41 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: two questions: special character and latex (18 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: two questions: special character and latex (36 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>
updating duplicates in a master data setRe: updating duplicates in a master data set (140 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (21 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: updating duplicates in a master data set (44 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: updating duplicates in a master data set (14 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: updating duplicates in a master data set (49 lines) From: Data _null_; <iebupdte@GMAIL.COM>